Skip to content

Update module google.golang.org/protobuf to v1.33.0 - autoclosed - #98

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/google.golang.org-protobuf-1.x
Closed

Update module google.golang.org/protobuf to v1.33.0 - autoclosed#98
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/google.golang.org-protobuf-1.x

Conversation

@renovate

@renovaterenovateBot commented Mar 8, 2024

Copy link
Copy Markdown
Contributor

Mend Renovate

This PR contains the following updates:

PackageChangeAgeAdoptionPassingConfidence
google.golang.org/protobufv1.32.0 -> v1.33.0ageadoptionpassingconfidence

Release Notes

protocolbuffers/protobuf-go (google.golang.org/protobuf)

v1.33.0

Compare Source


Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovaterenovateBot changed the title Update module google.golang.org/protobuf to v1.33.0Update module google.golang.org/protobuf to v1.33.0 - autoclosedMar 13, 2024
@renovaterenovateBot closed this Mar 13, 2024
@renovate
renovateBot deleted the renovate/google.golang.org-protobuf-1.x branch March 13, 2024 23:27
bootjp added a commit that referenced this pull request Apr 30, 2026
- Adapters fields are now *Adapter pointers (Gemini #98). Nil ->
excluded, non-nil empty -> included-with-no-scopes, non-nil
populated -> normal. Previous non-pointer struct collapsed both
"excluded" and "included-empty" into the same on-disk shape;
gemini's reference (don't silently drop entries during
serialization) was the right call. Test
TestAdaptersStruct_NilVsEmptyDistinguishedOnDisk covers it.
- KeymapReader.Next now validates the base64-encoded `original`
field at parse time (Codex P1 #179). Previously the JSON parsed
fine and the bad base64 surfaced lazily on Original() — that
defers corruption detection past initial ingest. Test
TestKeymapReader_RejectsMalformedBase64AtParseTime locks in the
parse-time validation.
- ReadManifest now rejects trailing bytes via dec.More() (Codex P2
#194). Two manifests concatenated, garbage tails, partial-write
artifacts: all surface as ErrInvalidManifest. Tests
TestReadManifest_RejectsTrailingBytes and
TestReadManifest_RejectsTrailingNonWhitespace.
- Test name TestKeymapReader_AcceptsBlankLinesByPolicy renamed to
TestKeymapReader_RejectsBlankLines (Gemini #160). The test was
already asserting rejection; only the name was misleading.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants