Skip to content

ci: start publishing @google-cloud/adapter-nextjs - #717

Merged
abhis3 merged 1 commit into
mainfrom
chore/release-google-cloud-adapter-nextjs
Nov 11, 2026
Merged

abhis3 merged 1 commit into
mainfrom
chore/release-google-cloud-adapter-nextjs

Conversation

@abhis3

@abhis3 abhis3 commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

What

Removes @google-cloud/adapter-nextjs from unreleasedPackages in scripts/github.js, so it gets canary and tagged releases like the other packages. Publishing goes through OSS Exit Gate only (#715), and the Exit Gate project config already lists this package.

The unreleasedPackages list stays, now empty, for the next package that needs CI before it ships.

What changes after this merges

  • Pushes to main that touch packages/@google-cloud/adapter-nextjs publish 0.1.0-canary.<sha> with the canary npm tag, after the usual release approval.
  • A GitHub release tagged @google-cloud/adapter-nextjs-v0.1.0 publishes 0.1.0 with the latest tag. Scoped tags match only that package, and unscoped adapter-nextjs-v* tags still match only @apphosting/adapter-nextjs.
  • Manual publish-exit-gate.yml runs can filter to this package.
  • Merging this PR publishes nothing by itself. It only changes a root script, so its push run has no package in scope.

Nothing changes for the other packages.

Release order

npm points latest at the first version a package ever publishes, whatever tag it's published with. So the first publish should be the 0.1.0 release, cut right after this merges and before any canary of this package is approved.

Testing

Dry runs of scripts/publish.js (PUBLISH_DRY_RUN=true) on e3d37c4, before and after this change:

Case Before After
Push to main that changes the package (HEAD^1..HEAD is #714) empty manifest @google-cloud/adapter-nextjs@0.1.0-canary.e3d37c4, tag canary
Release tag @google-cloud/adapter-nextjs-v0.1.0 lerna list fails (--scope and --ignore cancel out) only @google-cloud/adapter-nextjs@0.1.0, tag latest
Release tag adapter-nextjs-v14.0.22 only @apphosting/adapter-nextjs@14.0.22 same
Manual run with package=@google-cloud/adapter-nextjs lerna list fails 0.1.0-canary.e3d37c4.<run_id>.<attempt>, tag canary
Push of this commit (root script only) n/a empty manifest

npm pack --dry-run after npm run build gives 31 files (42.7 kB): README.md, package.json and dist/ (including dist/index.js and dist/serve.js). npm run lint:quiet passes.

Remove @google-cloud/adapter-nextjs from unreleasedPackages so that it
gets canary and tagged releases through OSS Exit Gate like the other
packages. The list stays, now empty, for the next package that needs CI
before it ships.
@abhis3 abhis3 self-assigned this Nov 11, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request updates the scripts/github.js file to remove @google-cloud/adapter-nextjs from the list of unreleased packages, indicating it is now ready for release. I have no further feedback to provide as there are no review comments or issues identified.

@abhis3
abhis3 marked this pull request as ready for review November 11, 2026 19:36
@abhis3
abhis3 merged commit 984d1fd into main Nov 11, 2026
21 checks passed
@abhis3
abhis3 deleted the chore/release-google-cloud-adapter-nextjs branch November 11, 2026 20:08
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.

2 participants