fix(release): create tags through API#282
Merged
Merged
Conversation
The checkout intentionally omits persisted Git credentials. Use the\nauthenticated GitHub API instead of an HTTPS Git push.
valentinfernandez1
approved these changes
Jul 15, 2026
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.
Summary
Why
The recovered 0.4.0 release published successfully, then failed in
Create release tagsbecause the HTTPS Git push could not authenticate withpersist-credentials: false.The missing
@parity/truapi@0.4.0tag and GitHub Release were repaired manually at the original release SHA. This change prevents the same partial failure when #278 releases@parity/truapi-host@0.1.0.Validation
gh apitag creation call successfully restored the 0.4.0 tag