Bump capi fork to v3.222.1-typed-includes.1 (clean upstream base) - #5449
Merged
norman-abramovitz merged 1 commit intoJun 15, 2026
Merged
Conversation
Repoints the fivetwenty-io/capi replace directive from the v3.216.8-typed-includes.2 pre-release to v3.222.1-typed-includes.1. The new tag is the typed-includes wave rebased onto upstream's merged async/quota fixes (#7/#9/#10), verified-compatible with CF API v3.222.0 via the capi-contract audit. It is a pre-release of v3.222.1 so that the eventual upstream v3.222.1 release (requested in capi PR #11) cleanly supersedes it and the replace directive can retire. Behavior-equivalent dependency swap; jetstream builds clean.
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
2 participants
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.
Repoints the
fivetwenty-io/capireplace directive from thev3.216.8-typed-includes.2pre-release tov3.222.1-typed-includes.1.The new fork tag is the typed-includes wave rebased onto upstream's merged async/quota fixes (
fivetwenty-io/capi#7/#9/#10), so it's a cleaner base than the prior216.8lineage (no fork-private copies of those fixes). It is verified-compatible with CF API v3.222.0 via thecapi-contractaudit — the 3.216→3.222 contract diff adds no new client surface (description-only param wording + empty request-body markers), and the only real gaps found were the async/quota fixes (now upstream) and the typed includes/fields (the wave itself).The tag is a pre-release of
v3.222.1by design: the upstream PR (fivetwenty-io/capi#11) requests a plainv3.222.1release, which will cleanly supersede this pre-release so the replace directive can retire in a one-line follow-up.Scope: behavior-equivalent dependency swap.
go.modreplace +go.sumonly.Verification:
go mod tidyresolves the tag;go build ./...clean insrc/jetstream.