use GitHub module path - #108
Merged
Merged
Conversation
alixander
force-pushed
the
agent/use-github-module-path
branch
from
August 9, 2026 07:09
8ed6dfa to
8524a50
Compare
alixander
marked this pull request as ready for review
August 9, 2026 07:11
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
1 participant
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.
What changed\n\n- Change the active Go module identity from oss.terrastruct.com/d2-playground to github.com/d2lang/d2-playground.\n\n## Why\n\nThe repository now lives in the d2lang organization and has no known consumers of the old vanity module path. Using the GitHub path removes the active Playground build dependency on Terrastruct DNS.\n\nThe previously published old-path pseudo-version remains immutable in the Go proxy.\n\n## Validation\n\n- go list ./...\n- COLOR=1 ./make.sh\n- git diff --check\n\nAfter merge, successful default-branch CI will trigger the production deploy; that deploy will also serve as the post-cutover Playground deployment proof.