Skip to content

Build VPC networking on released compute and networking - #22

Merged
scotwells merged 1 commit into
mainfrom
chore/pin-released-dependencies
Sep 16, 2026
Merged

scotwells merged 1 commit into
mainfrom
chore/pin-released-dependencies

Conversation

@scotwells

Copy link
Copy Markdown
Collaborator

The VPC controller now builds against published releases of compute (v0.8.0), network (v0.1.0), and network-services-operator (v0.27.0) instead of untagged commits. Its compute dependency was pinned to August's code, well behind the release.

No behavior change: the Instance fields VPC attachment reads are unchanged in compute v0.8.0, and no code changes were needed.

🤖 Generated with Claude Code

Cloud pinned all three modules to pseudo-versions. The
network-services-operator pin pointed at the head of an unmerged branch,
so a force-push or branch deletion would have broken `go mod download`.
That change merged and has shipped, and compute and network now publish
releases too. Pinning to tags gives reproducible module downloads and
makes the dependency versions readable.

- compute v0.8.0, network v0.1.0, network-services-operator v0.27.0
- Drop the stale UNMERGED comment on the NSO pin
- Keep the go.miloapis.com/ipam replace: the vanity import path does not
  resolve without it
- Indirect bumps (go-openapi/swag, x/net, x/text, miloapis locations)
  are what the new releases require

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@scotwells
scotwells requested a review from a team as a code owner September 16, 2026 23:02
@scotwells
scotwells merged commit 0e97aff into main Sep 16, 2026
8 checks passed
@scotwells
scotwells deleted the chore/pin-released-dependencies branch September 16, 2026 23:09
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