ci(release): checkout repository before creating release#2
Merged
bochkov-anton merged 1 commit intomainfrom Apr 24, 2026
Merged
ci(release): checkout repository before creating release#2bochkov-anton merged 1 commit intomainfrom
bochkov-anton merged 1 commit intomainfrom
Conversation
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.
Title:
ci(release): checkout repository before creating release
Body:
Summary
Fixes the tag-driven release workflow by checking out the repository before running
gh release create --verify-tagor any git-based validation.The previous workflow failed because GitHub CLI attempted to run git commands in a job workspace that did not contain a
.gitdirectory.Changes
actions/checkout@v5to the release job.fetch-depth: 0so release validation has access to repository history and tags.Release behavior
This change does not make the workflow create tags automatically.
The release flow remains:
main;main;release.ymlcreate the GitHub Release.Validation
go test ./...Notes
The failed release can be rerun after this fix is merged into
main, if GitHub uses the updated workflow definition for the tag run. If rerun still uses the old workflow definition, create a new patch tag frommain.