Skip to content

Put latest tag only when tags are pushed [TR-4419]#8

Merged
blu3r4y merged 2 commits intomainfrom
task/TR-4419-fix-install-versions
Apr 18, 2025
Merged

Put latest tag only when tags are pushed [TR-4419]#8
blu3r4y merged 2 commits intomainfrom
task/TR-4419-fix-install-versions

Conversation

@blu3r4y
Copy link

@blu3r4y blu3r4y commented Apr 18, 2025

The GitHub action should only put the latest tag when a new semver (i.e., a new tag) is released, and not whenever we push to main. Additionally, the docs should pin the version and not directly reference the latest main branch.

Also, there was an error with the goimports linter task, as it was referencing an incorrect path.

@blu3r4y blu3r4y added the build Affecting the build or release process label Apr 18, 2025
@blu3r4y blu3r4y self-assigned this Apr 18, 2025
@blu3r4y blu3r4y changed the title [TR-4419] Put latest tag only when tags are pushed Put latest tag only when tags are pushed [TR-4419] Apr 18, 2025
@blu3r4y blu3r4y merged commit 306201d into main Apr 18, 2025
4 checks passed
@blu3r4y blu3r4y deleted the task/TR-4419-fix-install-versions branch April 18, 2025 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Affecting the build or release process

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants