Repository navigation
release: 0.2.1 - #9
Merged
Merged
Conversation
Patch release picking up the merged Dependabot updates. - package.json / package-lock.json -> 0.2.1 - CHANGELOG: [0.2.1] entry for the @google-cloud/bigquery 9.0.2 lockfile pin - README status line -> 0.2.1 The setup-node 7.1.0 bump (#8) is CI-only and not consumer-facing, so it is left out of the CHANGELOG. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Patch release picking up the Dependabot updates merged today. It changes the version and CHANGELOG only, with no source changes.
What ships in 0.2.1
@google-cloud/bigquerylockfile pin 9.0.1 → 9.0.2 (chore(deps): Bump @google-cloud/bigquery from 9.0.1 to 9.0.2 in the minor-and-patch group #7). The declared range^9.0.1is unchanged, so consumers don't need to do anything.actions/setup-node7.0.0 → 7.1.0 (#8) only affects CI, so it isn't in the CHANGELOG.Verified
npm ci+npm test→ 42/42 passing, andnpm audit --omit=dev→ 0 vulnerabilitiesnpm pack --dry-run→ 9 files, version 0.2.1latest=0.2.0, so0.2.1is a new version, not a republishAfter merge
Tag
v0.2.1on the merge commit and push it. That startspublish.yml, which waits for approval in thenpmenvironment before publishing.🤖 Generated with Claude Code