Depend on IPAM by its published module path - #24
Merged
Merged
Conversation
go.miloapis.com/ipam now resolves (datum-cloud/go-imports#66), so the replace to the GitHub repository is no longer needed to fetch the v0.4.0 release. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
scotwells
force-pushed
the
chore/ipam-vanity-path
branch
from
September 17, 2026 00:26
078af0f to
b09143a
Compare
slindseysr
approved these changes
Sep 17, 2026
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.
VPC networking now depends on IPAM by its published module path instead of redirecting to the GitHub repository. The path resolves since datum-cloud/go-imports#66, so the redirect is no longer needed. IPAM stays on v0.4.0 from #23.
No behavior change.
🤖 Generated with Claude Code