ci: adjust outputs of changeset releases to reattempt most recent releases

[zimeg]

Summary

This pull request recovers a release that silently failed to publish and fixes the underlying workflow bug.

• The changesets/action v1→v2 bump (chore(deps): bump changesets/action from 1.9.0 to 2.1.1 #2714) migrated the action's inputs to kebab-case, but the release workflow still read the action's outputs by their old camelCase names. v2 renamed the outputs too (Rename to kebab-case for root action inputs and outputs changesets/action#668).
• With outputs.hasChangesets reading empty, the has-changesets == 'false' gate never matched, the "Check if publish is needed" step was skipped, and the publish job's gate failed closed. Release PR chore: release #2713 merged and bumped versions on main but never published to npm (@slack/web-api and @slack/webhook on main were ahead of the npm latest tags).
• Reverts chore: release #2713 to roll @slack/web-api back to 8.1.0 and @slack/webhook back to 8.0.1 (matching npm) and restores the consumed changeset, so a corrected release run republishes them cleanly.
• Fixes the three action-output reads in release.yml, using bracket notation because hyphenated keys cannot be dot-dereferenced in Actions expressions:
  • outputs.hasChangesets → outputs['has-changesets']
  • outputs.publishedPackages → outputs['published-packages']
  • outputs.published was not renamed in v2 and is left unchanged.

Testing

• After merge, confirm the release run's Changelog job does not skip "Check if publish is needed", and that the Publish job runs (not skipped).
• Confirm @slack/web-api@8.1.1 and @slack/webhook@8.0.2 publish to npm and get GitHub releases.

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]

🦋 Changeset detected

Latest commit: c316f5f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@slack/web-api	Patch
@slack/webhook	Patch

Not sure what this means? Click here to learn what changesets are.

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.21%. Comparing base (05502d9) to head (c316f5f).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2718   +/-   ##
=======================================
  Coverage   89.21%   89.21%           
=======================================
  Files          65       65           
  Lines       10393    10393           
  Branches      473      473           
=======================================
  Hits         9272     9272           
  Misses       1089     1089           
  Partials       32       32           

Flag	Coverage Δ
cli-hooks	89.21% <ø> (ø)
cli-test	89.21% <ø> (ø)
logger	89.21% <ø> (ø)
oauth	89.21% <ø> (ø)
socket-mode	89.21% <ø> (ø)
web-api	89.21% <ø> (ø)
webhook	89.21% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[zimeg]

💡 A comment or two of some thoughts ongoing.

[zimeg]

📚 note: This is returned from the most recent #2713 in hopes the next release will find our expected versions and not skip patches.

[zimeg]

🐷 note: This returns to the current latest. I'm not wishing to skip versions if the tag never landed!