[abhis3]

Summary

Stops publishing create-next-on-firebase. It was last published in May 2024 and gets about 40 downloads a month. Its npm maintainers don't include the account that publishes this repo's packages, so neither the current publish path nor OSS Exit Gate can publish it.

This adds it to unreleasedPackages in scripts/github.js:

• CI still builds and tests it whenever it changes.
• Publish runs skip it, in both the Wombat and Exit Gate modes.
• A create-next-on-firebase-v* release tag fails instead of publishing.

Testing

Local dry runs (npm run publish -- --use-oss-gate --dry-run):

• A manual run with no package filter lists every releasable package except @google-cloud/adapter-nextjs and create-next-on-firebase.
• Release tags still resolve as before: adapter-nextjs-v* → @apphosting/adapter-nextjs, firebase-frameworks-v* → firebase-frameworks.
• create-next-on-firebase-v* and package=create-next-on-firebase both fail before anything is staged.
• Lint and Prettier pass.

[gemini-code-assist]

Code Review

This pull request updates the scripts/github.js file to add the retired create-next-on-firebase package to the unreleasedPackages list, ensuring it is ignored during releases. There are no review comments, so no additional feedback is provided.

[abhis3]

Closing for now; we're not pursuing this change at the moment.