Skip to content

chore: always use the latest released version tag when building #13556

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

Merged
merged 2 commits into from
Jun 12, 2024

Conversation

kylecarbs
Copy link
Member

No description provided.

@kylecarbs kylecarbs self-assigned this Jun 12, 2024
@stirby
Copy link
Collaborator

stirby commented Jun 12, 2024

For posterity, our new bisected release channels have us release from a frozen branch rather than main. The go packages and deployments running from main were not listed under the latest version tag.

Thanks Kyle.

Copy link
Member

@deansheather deansheather left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but I haven't tried it on a variety of different commits

Co-authored-by: Dean Sheather <dean@deansheather.com>
@kylecarbs
Copy link
Member Author

@mafredri merging but if I overlooked anything please feel free to revert/edit!

@kylecarbs kylecarbs merged commit 1ca5dc0 into main Jun 12, 2024
27 checks passed
@kylecarbs kylecarbs deleted the latest-tag-ver branch June 12, 2024 18:52
@github-actions github-actions bot locked and limited conversation to collaborators Jun 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants