Repository navigation
chore(generator): refresh Gemfile.lock for google-apis-core 1.4.0 - #28303
Merged
Merged
Conversation
The weekly API regeneration failed again on 2026-10-25 with "Git checkout is not clean". google-apis-core 1.4.0 (released 10-22) also tightened its multi_json and representable requirements, but google-apis-generator's Gemfile.lock still records the local google-apis-core at 1.3.2. Bundler rewrites the lockfile during `generate-updates`, which leaves the checkout dirty, so the PR generator stops before the first API. This runs `bundle lock` (Bundler 4.0.14) in google-apis-generator: the local google-apis-core goes to 1.4.0 with its new requirements, and multi_json (1.21.2) and representable (3.3.1) move to the minimum versions those requirements allow. No gem release. This is the same one-time fix as #28168; a lasting fix is to update this lockfile whenever google-apis-core or google-apis-generator is released.
quartzmo
approved these changes
Oct 28, 2026
Member
|
Sounds good about the lasting fix for a post-release step to keep this lockfile in sync when core or generator releases, thank you! |
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.
The weekly API regeneration failed again on 2026-10-25 with "Git checkout is
not clean". google-apis-core 1.4.0 (released 10-22) also tightened its
multi_json and representable requirements, but google-apis-generator's
Gemfile.lock still records the local google-apis-core at 1.3.2. Bundler
rewrites the lockfile during
generate-updates, which leaves the checkoutdirty, so the PR generator stops before the first API.
This runs
bundle lock(Bundler 4.0.14) in google-apis-generator: the localgoogle-apis-core goes to 1.4.0 with its new requirements, and multi_json
(1.21.2) and representable (3.3.1) move to the minimum versions those
requirements allow. No gem release.
This is the same one-time fix as #28168; a lasting fix is to update this
lockfile whenever google-apis-core or google-apis-generator is released.