Skip to content

deps(go): bump the go-minor-and-patch group across 1 directory with 3 updates - #2

Merged
trendvidia merged 1 commit into
mainfrom
dependabot/go_modules/go-minor-and-patch-c42757c4da
May 7, 2026
Merged

deps(go): bump the go-minor-and-patch group across 1 directory with 3 updates#2
trendvidia merged 1 commit into
mainfrom
dependabot/go_modules/go-minor-and-patch-c42757c4da

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 7, 2026

Copy link
Copy Markdown
Contributor

Bumps the go-minor-and-patch group with 3 updates in the / directory: github.com/trendvidia/protoregistry, github.com/trendvidia/protowire-go and google.golang.org/grpc.

Updates github.com/trendvidia/protoregistry from 0.70.0 to 0.70.1

Changelog

Sourced from github.com/trendvidia/protoregistry's changelog.

[0.70.1] - 2026-05-06

Added

  • client.WithFallback(files, types) — configure parent *protoregistry.NamespacedFiles / *NamespacedTypes registries that the Resolver falls back to on a local miss. The namespace-wide aggregate and every per-schema view inherit the same parent, so well-known or shared types are visible from every lookup tier (FindDescriptorByName, FindMessageByName, FindFileByPath, FindExtensionByName, FindExtensionByNumber, and SchemaResolver.FindMessageByName).
  • client.WithParent(parent *Resolver) — convenience that chains another Resolver as the parent (passes its nsFiles / nsTypes through as fallback). Useful for modeling a "common types" namespace as the parent of per-tenant namespaces.
  • client.WithGlobalFallback() — fall back to upstream protoregistry.GlobalFiles / GlobalTypes so the Resolver can resolve both registry-managed and statically-compiled proto types through the same API.

Changed

  • The Resolver-level Find* methods no longer short-circuit to NotFound on a local-name-index miss. They now delegate to the Resolver's nsFiles / nsTypes aggregates, which transparently walk the configured parent chain via the fork's hierarchical-fallback machinery. Behavior is unchanged when no fallback is configured (no parent → still NotFound).

Internal

  • client/snapshot.go: per-schema *NamespacedFiles / *NamespacedTypes are constructed with cfg.parentFiles / cfg.parentTypes as parents, so per-schema lookups reach the fallback chain too.
  • client/client.go: Pin inherits the parent's fallback configuration so well-known / shared types stay visible in pinned views. Documented the caveat that a pinned view over a still-refreshing parent will see new parent entries surface after Pin returns; callers wanting a fully-frozen pin must build an independent frozen parent and pass it via WithFallback.

Tests

  • TestIntegration/WithFallback_ResolvesParentTypes exercises the full fallback chain across all lookup tiers, including SchemaResolver, with a "commons" namespace configured as parent of a "fallback" namespace via client.WithParent.
Commits
  • 7e4f016 release: cut v0.70.1
  • aed460f client: configurable hierarchical fallback (WithFallback/WithParent/WithGloba...
  • 0b22c6e client: incremental aggregate refresh
  • b3876a9 client: replace cross-schema for-loops with namespace-wide aggregates
  • 7b110d9 client: store descriptors in NamespacedFiles/NamespacedTypes
  • 1b5f13f chore: silence golangci-lint findings
  • cf0dd6d deps: bump protowire-go to v0.70.1
  • 259e966 initial public release
  • See full diff in compare view

Updates github.com/trendvidia/protowire-go from 0.70.2 to 0.70.3

Release notes

Sourced from github.com/trendvidia/protowire-go's releases.

v0.70.3 — PXF parser stricter on key forms

Patch release within the 0.70.x wire-contract line: the wire output is unchanged, only inputs that were never schema-valid are now rejected at parse time. Mirrors the upstream grammar tightening in trendvidia/protowire@8262bbb (docs/grammar.ebnf, docs/draft-trendvidia-protowire-00.txt).

Changed (breaking at the parser layer; non-breaking on the wire)

  • = (field assignment) and { … } (submessage) now require an identifier key. Inputs like 123 = 234 or child { 123 = 123 } are now parse errors with:

    field assignment with '=' requires an identifier key, got integer ("123"); use ':' for map entries

  • : (map entry) is rejected at the document top level — the document represents a proto message, never a map<K,V>. Use = for top-level field assignments. Map literals (field = { 1: "x" }) still work because : remains valid inside { … } blocks.

Cross-port status

Companion 0.70.0 releases for the rest of the protowire-* stack are in flight (PRs filed against protowire-cpp, protowire-rust, protowire-swift, protowire-dart, protowire-java, protowire-typescript; Python is covered transitively through the C++ FFI). Once those merge, every port at any 0.70.x version implements the same wire contract — the protowire stack's cross-port wire-equivalence promise.

Install

go get github.com/trendvidia/protowire-go@v0.70.3

See CHANGELOG.md for the full diff against v0.70.2.

Changelog

Sourced from github.com/trendvidia/protowire-go's changelog.

[0.70.3] — 2026-05-06

Parser-strictness release. Stays inside the 0.70.x wire-contract line: the wire output is unchanged, only inputs that were never schema-valid are now rejected at parse time.

Changed (breaking)

  • PXF parser stricter on key forms, mirroring the upstream grammar tightening in trendvidia/protowire@8262bbb (docs/grammar.ebnf, docs/draft-trendvidia-protowire-00.txt):
    • = (field assignment) and { … } (submessage) now require an identifier key. Inputs like 123 = 234 or child { 123 = 123 } are now parse errors with "field assignment with '=' requires an identifier key, got integer (\"123\"); use ':' for map entries".
    • : (map entry) is rejected at document top level — the document represents a proto message, never a map<K,V>. Use = for top-level field assignments. Map literals (field = { 1: "x" }) still work because : remains valid inside { … } blocks.
Commits
  • d21212e release: cut v0.70.3
  • 0d2fc3c Merge pull request #4 from trendvidia/feat/strict-pxf-keys
  • d8bf7b7 pxf: enforce identifier-only key for '='/'{}'; reject top-level ':'
  • 05eaf42 Merge pull request #3 from trendvidia/dependabot/github_actions/actions/setup...
  • b9cf1d8 deps(deps): bump actions/setup-go from 5 to 6
  • See full diff in compare view

Updates google.golang.org/grpc from 1.80.0 to 1.81.0

Release notes

Sourced from google.golang.org/grpc's releases.

Release 1.81.0

Behavior Changes

  • balancer/rls: Switch gauge metrics to asynchronous emission (once per collection cycle) to reduce telemetry noise and align with other gRPC language implementations. (#8808)

Dependencies

  • Minimum supported Go version is now 1.25. (#8969)

Bug Fixes

  • xds: Use the leaf cluster's security config for the TLS handshake instead of the aggregate cluster's config. (#8956)
  • transport: Send a RST_STREAM when receiving an END_STREAM when the stream is not already half-closed. (#8832)
  • xds: Fix ADS resource name validation to prevent a panic. (#8970)

New Features

  • grpc/stats: Add support for custom labels in per-call metrics (gRFC A108). (#9008)
  • xds: Add support for Server Name Indication (SNI) and SAN validation (gRFC A101). Disabled by default. To enable, set GRPC_EXPERIMENTAL_XDS_SNI=true environment variable. (#9016)
  • xds: Add support to control which fields get propagated from ORCA backend metric reports to LRS load reports (gRFC A85). Disabled by default. To enable, set GRPC_EXPERIMENTAL_XDS_ORCA_LRS_PROPAGATION=true. (#9005)
  • xds: Add metrics to track xDS client connectivity and cached resource state (gRFC A78). (#8807)
  • stats/otel: Enhance grpc.subchannel.disconnections metric by adding disconnection reason to the grpc.disconnect_error label (gRFC A94). This provides granular insights into why subchannels are closing. (#8973)
  • mem: Add mem.Buffer.Slice() API to slice the buffer like a slice. (#8977)

Performance Improvements

  • alts: Pool read buffers to lower memory utilization when sockets are unreadable. (#8964)
  • transport: Pool HTTP/2 framer read buffers to reduce idle memory consumption. Currently limited to Linux for ALTS and non-encrypted transports (TCP, Unix). To disable, set GRPC_GO_EXPERIMENTAL_HTTP_FRAMER_READ_BUFFER_POOLING=false and report any issues. (#9032)
Commits
  • cb18228 Change version to 1.81.0 (#9062)
  • 96748f9 Cherry-pick #9105 to 1.81.x (#9106)
  • 9183222 Cherry pick #9055, #9032 to v1.81.x (#9095)
  • 5cba6da Revert "deps: update dependencies for all modules (#9065)" (#9067)
  • af8a936 deps: update dependencies for all modules (#9065)
  • cdc60df transport: optimize heap allocations in ready reader and update syscall conne...
  • 208d053 xds/resolver: pass complete XDSConfig in RPC context for HTTP filters (gRFC A...
  • 50fe1cc test: Fix flaky test TestServerStreaming_ClientCallRecvMsgTwice in `end2end...
  • d574bad build(deps): bump go.opentelemetry.io/otel/sdk from 1.42.0 to 1.43.0 (#9050)
  • b8bf4d0 build(deps): bump go.opentelemetry.io/otel/sdk from 1.42.0 to 1.43.0 in /inte...
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels May 7, 2026
… updates

Bumps the go-minor-and-patch group with 3 updates in the / directory: [github.com/trendvidia/protoregistry](https://github.com/trendvidia/protoregistry), [github.com/trendvidia/protowire-go](https://github.com/trendvidia/protowire-go) and [google.golang.org/grpc](https://github.com/grpc/grpc-go).


Updates `github.com/trendvidia/protoregistry` from 0.70.0 to 0.70.1
- [Release notes](https://github.com/trendvidia/protoregistry/releases)
- [Changelog](https://github.com/trendvidia/protoregistry/blob/main/CHANGELOG.md)
- [Commits](trendvidia/protoregistry@v0.70.0...v0.70.1)

Updates `github.com/trendvidia/protowire-go` from 0.70.2 to 0.70.3
- [Release notes](https://github.com/trendvidia/protowire-go/releases)
- [Changelog](https://github.com/trendvidia/protowire-go/blob/main/CHANGELOG.md)
- [Commits](trendvidia/protowire-go@v0.70.2...v0.70.3)

Updates `google.golang.org/grpc` from 1.80.0 to 1.81.0
- [Release notes](https://github.com/grpc/grpc-go/releases)
- [Commits](grpc/grpc-go@v1.80.0...v1.81.0)

---
updated-dependencies:
- dependency-name: github.com/trendvidia/protoregistry
  dependency-version: 0.70.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-minor-and-patch
- dependency-name: github.com/trendvidia/protowire-go
  dependency-version: 0.70.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-minor-and-patch
- dependency-name: google.golang.org/grpc
  dependency-version: 1.81.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title deps(go): bump the go-minor-and-patch group with 3 updates deps(go): bump the go-minor-and-patch group across 1 directory with 3 updates May 7, 2026
@dependabot
dependabot Bot force-pushed the dependabot/go_modules/go-minor-and-patch-c42757c4da branch from eb13adf to 579466f Compare May 7, 2026 03:54
@trendvidia
trendvidia merged commit 5950b75 into main May 7, 2026
4 checks passed
@trendvidia
trendvidia deleted the dependabot/go_modules/go-minor-and-patch-c42757c4da branch May 7, 2026 08:50
trendvidia added a commit that referenced this pull request May 14, 2026
Closes the README's schema-resolution-chain item #2: @proto directives
in the input document are now compiled into the descriptor registry,
alongside whatever -p schema.proto provides. A self-describing PXF
file with @proto + @dataset works without any flags — the
schema travels with the data, as the v1.0 spec freeze intended.

Three of the four @proto body shapes are honoured as schema sources
(draft §3.4.5):

  * named      `@proto Name { body }`       — sugar wrapped into a
                                              standalone .proto (package
                                              + message) and fed to
                                              protocompile alongside -p
  * source     `@proto """ <.proto> """`    — full .proto source file,
                                              served to protocompile via
                                              an in-memory Accessor
  * descriptor `@proto b"<base64-FDSet>"`   — proto.Unmarshal +
                                              protodesc.NewFiles; no
                                              compile step

  * anonymous  `@proto { body }`            — rejected for now with an
                                              actionable error string;
                                              its bind-to-next-typeless
                                              rule lands in a follow-up.

Implementation detail: protocompile.SourceResolver gets a custom
Accessor so virtual filenames (`__pxq_indoc_N.proto`) serve from an
in-memory map, while regular filenames passed via -p fall through to
os.Open. This lets cross-references between in-doc and -p protos work
in a single compile pass without temp-file gymnastics.

Validation:
* 52 Go tests (45 from prior stages + 7 new) covering each of the
  three working shapes (named, source, descriptor), the anonymous
  rejection, named-with-no-package edge case, and the combined
  -p + in-doc resolution.
* End-to-end smoke against a self-describing PXF document: the
  README's quick-start example with @proto trades.v1.Trade + @dataset
  now does the right thing under `pxf_proto(...)` with no `-p` flag:
    @type trades.v1.Trade
    price = ...
    qty = ...
    symbol = "..."

Follow-ups still queued: anonymous @proto binding, bundled canonical
schemas (pxf/*, sbe/*, envelope/v1/*), protoregistry resolution
(-s/-n/--schema), and the strict-mode compile-time AST validator.
trendvidia added a commit that referenced this pull request Jul 16, 2026
trendvidia added a commit that referenced this pull request Jul 16, 2026
* spec: ratify RFC-001 (issue #56)

Status Draft → Ratified (2026-07-16). §13 rows 13/14 now cite their
tracking issues (GH #111, #112) — with those filed, every open
question is either resolved in the RFC (S1: #11#16; S2: #15
source grammar, #21 sensitivity, #35 path scheme; S3: #22
engine-expression scope, #23 no dual-emission) or tracked as a
separate issue (GH #59, #66#69, #103, #111, #112). All v1.2 surface
is strictly additive; no locked decision blocks an existing port's
roadmap (per-port adoption is M9+, gated on the conformance corpus).

* docs: record #2 ratification (GH #56, PR #113)
@trendvidia trendvidia mentioned this pull request Jul 16, 2026
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant