From 427c251dc942a08cc94320d4fd131c9c28a05ffb Mon Sep 17 00:00:00 2001 From: Abhinav Sundaresan Date: Mon, 9 Nov 2026 22:18:30 +0000 Subject: [PATCH] chore: stop publishing create-next-on-firebase create-next-on-firebase hasn't been published since May 2024 and gets about 40 downloads a month. Its npm maintainers don't include the account that publishes this repo's packages, so it can't be published anymore. Adding it to unreleasedPackages keeps it in CI builds and tests, while publish runs and release tags skip it. --- scripts/github.js | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/scripts/github.js b/scripts/github.js index 629a97dbc..a72dfede2 100644 --- a/scripts/github.js +++ b/scripts/github.js @@ -15,8 +15,9 @@ const since = const lernaList = JSON.parse(execSync("lerna list --json --loglevel silent")); -// Packages that CI builds and tests but that this repo doesn't release or publish yet. -const unreleasedPackages = ["@google-cloud/adapter-nextjs"]; +// Packages that CI builds and tests but that this repo doesn't publish: packages that aren't +// released yet, and create-next-on-firebase, which is retired. +const unreleasedPackages = ["@google-cloud/adapter-nextjs", "create-next-on-firebase"]; const ignoreUnreleased = unreleasedPackages.map((pkgName) => `--ignore='${pkgName}'`).join(" "); // Unscoped release tags (e.g. adapter-nextjs-v14.0.22, firebase-frameworks-v0.11.9) match only