### What needs to get done For the artefact metadata of CRAFT packages, we currently use the `version` from the *craft.yaml file in the git repo commit that was pulled in, and store that in artefact `metadata.version`. Instead of doing this, store the commit hash that was pulled in, and store this in the artefact `metadata.version`, similar format to `application/x.canonical.snap-package` (but not using the revision this time). ### Why it needs to get done It's useful for machine-consumers of the Fetch Service Metadata to be able to know what commit of the CRAFT package was pulled into a build, so that they may ie. query the Store for info on the CRAFT package revision. Currently, getting the CRAFT package commit is only obtainable from the "craft" "inspector annotations (looking at the "checkout" commit) e.g. ``` "craft.sourcecraft": { "opinion": "Approved", "reason": "sourcecraft repository found", "annotations": { "checkout": "0ac1768502a1966167a289ab046645d547b72461" } ``` However, annotations are meant for human-consumption, so machines should avoid parsing these, hence the need for this change. It may also be worth considering extending the artifact metadata format in general to include an additional "revision" or "commit" field or similar, in order to allow for this info to exist alongside the "version" field, and have the "version" field match the version in the *craft YAML.