feat(release-to-candidate): Support projects that doesn't specify the version
property
#46
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is possible that the Snapcraft project doesn't specify the
version
property in the snapcraft.yaml, instead of setting the snap version string via thecraftctl set version=_version_
mechanism. In this case, the parse-snapcraft-yaml job will set the version variable tonull
, making the release-to-candidate job unable to detect the built snap due to a filename mismatch:This patch enhances the release-to-candidate job so that the built snap will still be matched via filename matching.
Although projects that don't specify the
version
property aren't really compliant with the Snapcrafters policy, supporting this use case allows external projects to reuse the snapcrafters/ci/release-to-candidate GitHub Action job without the need to fork the project.