Overview

Eighth attempt at testing the pre-release workflow. Previous attempts failed due to:

• fix: test prerelease workflow #1219: release workflow checked out main instead of next
  • Fixed in ci: fix release workflow checkout for next branch #1221
• fix: test prerelease workflow (take 2) #1222: shallow clone missing branch refs for semantic-release
  • Fixed in ci: fetch full git history for semantic-release #1223
• fix: test prerelease workflow (take 3) #1225: detached HEAD preventing semantic-release from resolving branch refs
  • Fixed in ci: use branch ref for release workflow checkout #1226
• fix: test prerelease workflow (take 4) #1227: GITHUB_REF pointing to default branch in workflow_run events
  • Fixed in ci: override GITHUB_REF for semantic-release in workflow_run events #1228
• fix: test prerelease workflow (take 5) #1229: release workflow failed to run
  • Fixed in ci: fetch all branches and tags for semantic-release #1230
• fix: test prerelease workflow (take 6) #1231: published stable release v9.0.3 instead of pre-release (same GITHUB_REF issue)
  • Fixed in ci: debug and fix GITHUB_REF override for prerelease workflow #1232
• fix: test prerelease workflow (take 7) #1233: dry-run validated the fix (semantic-release correctly detected next and would publish 9.0.4-next.1)
  • Dry-run removed in ci: enable prerelease workflow for next branch #1234

Empty commit to verify that semantic-release publishes an actual pre-release from next.

Note: #1234 must be merged into main and next synced before merging this PR.

PR Checklist

• Pull request title follows the Conventional Commits Specification

Test plan

• Merge this PR into next
  • Observe that the release workflow publishes a pre-release version (e.g., 9.0.4-next.1) to npm and GitHub Packages