Fix releaser tag creation #62522
Merged
Fix releaser tag creation #62522
+24
−0
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
typescript-bot
added
Author: Team
For Uncommitted Bug
There was a problem hiding this comment.
Pull Request Overview
This PR fixes an issue where GitHub releases were being tagged against the main branch instead of the correct commit hash. The fix ensures that releases are properly tagged against the specific commit that was used to build the package.
- Extracts the git commit hash from the published package's
package.jsonfile - Uses this commit hash as the target for GitHub release creation
- Adds Node.js tooling to support reading the package metadata
DanielRosenwasser
approved these changes
Oct 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
When I moved the releaser, I did not specify the target of the release it creates, so it was just pointing to main each time. 😦
Read the package and then tag the gitHead we place in package.json.