Repository navigation
Conversation
adpeyre
force-pushed
the
feature/release-version
branch
from
October 30, 2026 12:33
d884a60 to
3cb4a4f
Compare
When set, `deploy:update_code` saves a human-readable version of the deployed target in this file, computed by `git describe --tags --always`: the tag pointing at it, the latest tag followed by the number of commits since and the abbreviated hash, or the abbreviated hash if there is no tag. `REVISION` still holds the full commit hash. The Sentry recipe uses this file as default release version.
adpeyre
force-pushed
the
feature/release-version
branch
from
October 30, 2026 13:07
3cb4a4f to
dacae10
Compare
This branch has not been deployed
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.
Add
release_version_fileoption to save the deployed tagDescription :
Why
REVISIONalways holds the commit hash. Applications often need a human-readable version (the git tag when one is deployed) to display it or to report it to an error tracker. Doing it from a project recipe is fragile: the recipe has to compute the version itself, usually on the local checkout, which may differ from whatdeploy:update_codeactually deployed (archiveandclonestrategies use the remote mirror).What
New option
release_version_file(disabled by default). When set,deploy:update_codesaves the version of the deployed target in{{release_path}}/{{release_version_file}}, computed where the revision is already computed (remote mirror or local checkout depending on the strategy):release_version_commandcomputes the version. Default: the tag pointing exactly at{{target}}, or its commit hash if there is none.release_versionreads it back, likerelease_revision.git_version_commandstill takes precedence. Commit tracking keeps usingREVISION.REVISIONis unchanged, sodeploy:check_remote,releasesand the Sentry commits range keep working with a commit hash.