fix: use new-release-version rather than new-release-git-tag, which does not exist#530
Merged
neilcampbell merged 1 commit intomainfrom Nov 22, 2025
Merged
fix: use new-release-version rather than new-release-git-tag, which does not exist#530neilcampbell merged 1 commit intomainfrom
neilcampbell merged 1 commit intomainfrom
Conversation
lempira
approved these changes
Nov 22, 2025
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
2 participants
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.
The release pipeline was failing, which appears to be using an incorrect value in the GH action.
Based on the below failure debug output,
new-release-git-tagis not a value that is ever set.https://github.com/algorandfoundation/algokit-lora/actions/runs/19595587688/job/56119938956#step:8:183