chore(ci): retarget release tags after squash-merge before npm publish [WPB-23275]#20490
chore(ci): retarget release tags after squash-merge before npm publish [WPB-23275]#20490thisisamir98 wants to merge 2 commits intodevfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds a new step to the publish-libraries-on-merge.yml GitHub Actions workflow that retargets release tags from the original PR head commit to the squash-merge commit before publishing to npm. The change aims to fix a scenario where tags become orphaned after a squash-merge operation.
Changes:
- Adds a "Retarget release tags to squash merge commit" step that force-moves git tags from the PR head SHA to the merge commit SHA
- Includes validation to ensure tags exist and match the expected library@version format
- Executes before the Node.js setup and npm publish steps
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #20490 +/- ##
==========================================
- Coverage 45.38% 45.38% -0.01%
==========================================
Files 1637 1637
Lines 40370 40370
Branches 8337 8337
==========================================
- Hits 18323 18322 -1
Misses 20112 20112
- Partials 1935 1936 +1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
|
🔗 Download Full Report Artifact 🧪 Playwright Test Summary
|



Pull Request
Summary
Security Checklist (required)
Accessibility (required)
Standards Acknowledgement (required)
Screenshots or demo (if the user interface changed)
Notes for reviewers