Skip to content

fix: publish one combined GitHub release - #1503

Open
ArekChr wants to merge 1 commit into
callstack:mainfrom
ArekChr:fix/single-github-release
Open

ArekChr wants to merge 1 commit into
callstack:mainfrom
ArekChr:fix/single-github-release

Conversation

@ArekChr

@ArekChr ArekChr commented Oct 19, 2026

Copy link
Copy Markdown

Summary

Changesets currently creates a GitHub release for every published package. Create one combined release on the existing main package tag instead, with notes collected from all packages in the fixed release group.

  • Disable per-package GitHub releases while keeping package tags and npm publishing managed by Changesets.
  • Combine changelog entries for the exact release version, list all released packages, and omit empty note sections. Include fixtures from 5.4.2.
  • Preserve an existing GitHub release and support retrying release creation after all package tags have reached GitHub.
  • Run the release automation tests in CI and document the release and retry behavior.

Validation

  • node --test .github/scripts/*.test.mjs — 18 tests passed, including 5.4.2 notes, one release for six packages, existing releases, and retry behavior.
  • Biome 2.5.6 check for .github/scripts and package.json — passed.
  • actionlint 1.7.7 for both changed workflows — passed.
  • git diff --check — passed.
  • Package build, typecheck, and full monorepo tests were not run locally.

Scope

This covers the current fixed group containing @callstack/repack. Missing or mismatched package tags require manual verification and repair before retrying; the script does not recover npm publications or recreate tags. Canary publishing is unchanged.

@vercel

vercel Bot commented Oct 19, 2026

Copy link
Copy Markdown

@ArekChr is attempting to deploy a commit to the Callstack Team on Vercel.

A member of the Team first needs to authorize it.

@changeset-bot

changeset-bot Bot commented Oct 19, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 42c734b

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

@ArekChr
ArekChr marked this pull request as ready for review October 19, 2026 08:10

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant