-
Notifications
You must be signed in to change notification settings - Fork 1.7k
tag with git hash #3965
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tag with git hash #3965
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@aojea @stmcginnis WDYT? |
|
you are the expert on these things |
|
I think we should, because the commit hash only changes if we rewrite history. |
|
Also I think the git tags detected are wrong on recently pushed base etc images (v0.29.0....) ... better to just drop that, we only need date-sha for uniqueness and traceability, we're not advertising semver in these images |
|
Yeah, makes sense to me. And good point about semver. I think that may have been misleading to some people. /lgtm |
Something changed and our automatic image builds now have fancy git describe output instead of just the date+hash.
This would ensure we keep using date+hash.
I think that's probably the best move for now.