Skip to content

fix(release-kit): drop dist-tag add on stable publish, prep fbe kit 0.1.1 #3220

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cabljac merged 2 commits into from
Sep 28, 2026
Merged

fix(release-kit): drop dist-tag add on stable publish, prep fbe kit 0.1.1 #3220

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fd86262
fix(release-kit): drop dist-tag add on stable publish
cabljac Sep 28, 2026
8aa8d55
docs(firestore-bigquery-export): CHANGELOG for kit 0.1.1
cabljac Sep 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 11 additions & 6 deletions .github/workflows/release-kit.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,12 @@ jobs:
permissions:
contents: read
steps:
- name: Print inputs
env:
INPUTS: ${{ toJSON(inputs) }}
run: |
echo "$INPUTS"

# Kits live only on the kits branch; the ref is pinned so dispatching
# from any branch (including next, which lists the workflow in the UI)
# releases the same content.
Expand Down Expand Up @@ -94,7 +100,7 @@ jobs:
run: |
npm ci
if [ "$USE_FIREBASE_FUNCTIONS_RC" = "true" ]; then
npm install --save firebase-functions@next
npm install --save --registry=https://registry.npmjs.org firebase-functions@next
fi
npm test

Expand Down Expand Up @@ -219,7 +225,7 @@ jobs:
else
NEW_VER=$(npx --yes semver@7.8.5 -i "$BUMP_LEVEL" "$HIGHEST_STABLE")
BUMP_TYPE="$BUMP_LEVEL"
TARGET_TAG="latest (and next)"
TARGET_TAG="latest"
fi

for v in $TAKEN; do
Expand All @@ -245,7 +251,7 @@ jobs:
run: |
npm ci --registry=https://registry.npmjs.org
if [ "$USE_FIREBASE_FUNCTIONS_RC" = "true" ]; then
npm install --save firebase-functions@next
npm install --save --registry=https://registry.npmjs.org firebase-functions@next
fi
npm run build

Expand Down Expand Up @@ -368,10 +374,9 @@ jobs:
if [ "$IS_PRERELEASE" = "true" ]; then
npm publish --tag next --provenance --access public $DRY_RUN_FLAG
else
# No `npm dist-tag add` here: the trusted-publishing token only
# authorises publish, so a dist-tag mutation fails with E401.
npm publish --tag latest --provenance --access public $DRY_RUN_FLAG
if [ "$DRY_RUN" != "true" ]; then
npm dist-tag add ${PKG_NAME}@${VERSION} next
fi
fi

# Pushed only after a successful publish: a failed publish leaves the
Expand Down
3 changes: 2 additions & 1 deletion kits/firestore-bigquery-export/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
## Version 0.1.0
## Version 0.1.1

- fix: 0.1.0 shipped the kit's devDependencies in its `npm-shrinkwrap.json`, so a consumer `npm ci` under npm 10 (the Cloud Functions buildpack) fails with `EBADPLATFORM` on the `@esbuild/*` platform binaries. 0.1.1 ships the pruned shrinkwrap. Do not use 0.1.0.
- Initial release of kit, see README for differences between the legacy extension and this kit
Comment on lines +1 to 4

@gemini-code-assist gemini-code-assist Bot Sep 28, 2026

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.

medium

Since 0.1.0 was already published to npm, it is best practice to keep its entry in the changelog as a separate section rather than replacing the version header. This maintains a clear, chronological history of all published versions, even if a version is deprecated or broken.

Suggested change
## Version 0.1.1
- fix: 0.1.0 shipped the kit's devDependencies in its `npm-shrinkwrap.json`, so a consumer `npm ci` under npm 10 (the Cloud Functions buildpack) fails with `EBADPLATFORM` on the `@esbuild/*` platform binaries. 0.1.1 ships the pruned shrinkwrap. Do not use 0.1.0.
- Initial release of kit, see README for differences between the legacy extension and this kit
## Version 0.1.1
- fix: 0.1.0 shipped the kit's devDependencies in its npm-shrinkwrap.json, so a consumer npm ci under npm 10 (the Cloud Functions buildpack) fails with EBADPLATFORM on the @esbuild/* platform binaries. 0.1.1 ships the pruned shrinkwrap. Do not use 0.1.0.
## Version 0.1.0
- Initial release of kit, see README for differences between the legacy extension and this kit

@cabljac cabljac Sep 28, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This CHANGELOG is the release notes for the next publish and the workflow clears it on a stable release, so it is not a running history. 0.1.0 never got a GitHub release, so its notes surface only through the 0.1.1 entry. Keeping the single section.

Loading