Skip to content

Switch capi to upstream v3.222.1, retire fork replace - #5451

Merged
norman-abramovitz merged 1 commit into
cloudfoundry:developfrom
nabramovitz:chore/capi-upstream-v3.222.1
Jun 15, 2026
Merged

Switch capi to upstream v3.222.1, retire fork replace#5451
norman-abramovitz merged 1 commit into
cloudfoundry:developfrom
nabramovitz:chore/capi-upstream-v3.222.1

Conversation

@nabramovitz

Copy link
Copy Markdown
Contributor

What

The typed query-options work (capi PR #11) merged upstream and was tagged v3.222.1, so the norman-abramovitz/fw-capi fork is no longer needed for the build.

  • Bump github.com/fivetwenty-io/capi/v3 require v3.216.6 → upstream v3.222.1
  • Drop the replace … => norman-abramovitz/fw-capi/v3 v3.222.1-typed-includes.1 directive

This completes the fork-retirement: #5449 pinned the fork tag temporarily while the upstream tag was pending; with v3.222.1 now published upstream, we collapse to a plain dependency.

Verification

  • go mod tidy resolves upstream v3.222.1; go.sum carries only the upstream module hash (no fork reference)
  • go build ./... clean

Two-file change (go.mod / go.sum); letting the PR gate validate.

The typed query-options work (capi PR #11) merged upstream and was
tagged v3.222.1, so the norman-abramovitz/fw-capi fork is no longer
needed for the build. Bump the require to upstream v3.222.1 and drop
the replace directive. go build ./... clean; go.sum now carries only
the upstream module hash.

@norman-abramovitz norman-abramovitz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@norman-abramovitz
norman-abramovitz merged commit 4812e8b into cloudfoundry:develop Jun 15, 2026
23 checks passed
@nabramovitz
nabramovitz deleted the chore/capi-upstream-v3.222.1 branch June 17, 2026 08:11
Sign up for free to 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.

2 participants