ci: skip publish step if no release is needed

[zimeg]

Summary

This PR skips the publish step if no release is needed 🚀

Fixes an issue where publishing is attempted after a recent release but no changsets exist. The "changelog" PR wasn't created so publishing was attempted! This didn't cause problems but requires unneeded approval.

Requirements

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c9b1539

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.59%. Comparing base (a24cf85) to head (c9b1539).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2894   +/-   ##
=======================================
  Coverage   93.59%   93.59%           
=======================================
  Files          44       44           
  Lines        7855     7855           
  Branches      687      687           
=======================================
  Hits         7352     7352           
  Misses        498      498           
  Partials        5        5           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 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.

[zimeg]

📸 Example of these pending actions:

[WilliamBergamin]

Nice find 💯

Left a non blocking comment

[WilliamBergamin]

Is there a reason we don't want to check for == 'false' instead?

Suggested change

	if: needs.changelog.outputs.hasChangesets == 'false' && needs.changelog.outputs.releaseExists != 'true'
	if: needs.changelog.outputs.hasChangesets == 'false' && needs.changelog.outputs.releaseExists != 'false'

[zimeg]

@WilliamBergamin Earlier iterations might've left odd patterns here! We landed a92b061 to continue if no release exists now with a false check 🏁

[zimeg]

@WilliamBergamin I appreciate the review toward more sensible logic 🧠 ✨

Let's merge this now and mirror this in adjacent projects to avoid required approvals for attempted releases before changes land 🚀