Skip to content

Comments

chore(ci): retarget release tags after squash-merge before npm publish [WPB-23275]#20490

Open
thisisamir98 wants to merge 2 commits intodevfrom
WPB-23275-14
Open

chore(ci): retarget release tags after squash-merge before npm publish [WPB-23275]#20490
thisisamir98 wants to merge 2 commits intodevfrom
WPB-23275-14

Conversation

@thisisamir98
Copy link
Collaborator

@thisisamir98 thisisamir98 commented Feb 23, 2026

TaskWPB-23275 [Web] Fix publish workflow

Pull Request

Summary

  • What did I change and why?
  • Risks and how to roll out / roll back (e.g. feature flags):

Security Checklist (required)

  • External inputs are validated & sanitized on client and/or server where applicable.
  • API responses are validated; unexpected shapes are handled safely (fallbacks or errors).
  • No unsafe HTML is rendered; if unavoidable, sanitization is applied and documented where it happens.
  • Injection risks (XSS/SQL/command) are prevented via safe APIs and/or escaping.

Accessibility (required)

Standards Acknowledgement (required)


Screenshots or demo (if the user interface changed)

Notes for reviewers

  • Trade-offs:
  • Follow-ups (linked issues):
  • Linked PRs (e.g. web-packages):

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link

codecov bot commented Feb 23, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 45.38%. Comparing base (8822c27) to head (f554c4e).
⚠️ Report is 1 commits behind head on dev.

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     
Flag Coverage Δ
app_webapp 43.56% <ø> (-0.01%) ⬇️
lib_api_client 50.50% <ø> (ø)
lib_core 58.86% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@sonarqubecloud
Copy link

@github-actions
Copy link
Contributor

🔗 Download Full Report Artifact

🧪 Playwright Test Summary

  • Passed: 10
  • Failed: 0
  • Skipped: 4
  • 🔁 Flaky: 0
  • 📊 Total: 14
  • Total Runtime: 82.1s (~ 1 min 22 sec)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants