Propose version suffix strategy for non-git snap builds#547
Closed
jonathan-conder with Copilot wants to merge 1 commit into
Closed
Propose version suffix strategy for non-git snap builds#547jonathan-conder with Copilot wants to merge 1 commit into
jonathan-conder with Copilot wants to merge 1 commit into
Conversation
13 tasks
Copilot
AI
changed the title
[WIP] Address feedback on git shortref suffix in snap build process
Propose version suffix strategy for non-git snap builds
Nov 21, 2025
Contributor
Yes this was basically my initial reasoning |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses feedback on handling snap version suffixes when building outside git context (e.g., from release tarballs).
Current behavior:
VERSION-<hash>for traceabilityVERSION-devfor development buildsVERSION(clean semantic version)Recommendation
No suffix for non-git builds. Release tarballs already contain the official version from
VERSIONfile. Git-based suffixes serve development/testing traceability; release builds don't need additional markers.Alternative
If explicit handling is preferred:
-sourceover-nogit. Indicates "built from source tarball" rather than exposing implementation details.Awaiting maintainer preference before implementing changes.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.