chore(update): repoint the CLI self-update source to DIG-Network/digs (#764)#29
Merged
Merged
Conversation
… (#764) Part 2 of the F2d reference sweep: digstore-cli's own `dig-store update` command resolves its release via RELEASES_API, which still hard-coded the pre-rename DIG-Network/dig-store GitHub API path -- the same real-breakage class as the installer/apt fixes already landed, just missed on the first pass (this repo's own consumers, not just its callers). Also repoints the two remaining dig-client-wasm doc/script refs (PUBLISHED_README.md, scripts/assemble-pkg.mjs) left over from the first pass's pkg/pkg-node gitignore exclusion. Co-Authored-By: Claude <noreply@anthropic.com>
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.
Summary
Part 2 of the F2d reference sweep (#764) -- found on a fuller ecosystem-wide grep after the first PR (#28) merged.
digstore-cli's owndig-store updateself-update command'sRELEASES_APIconstant still hard-coded the pre-renameDIG-Network/dig-storeGitHub API path (crates/digstore-cli/src/commands/update.rs) -- the same functional-breakage class already fixed in dig-installer/apt.dig.net, just missed on the first pass since it's a downstream CONSUMER inside this same repo, not a self-reference.Also catches two
dig-client-wasmdoc/script refs left over from the first pass'spkg/pkg-nodegitignore-exclusion sweep (PUBLISHED_README.md,scripts/assemble-pkg.mjs-- these are tracked source files, distinct from the gitignoredpkg//pkg-node/build output).Blast radius checked
RELEASES_APIhas exactly one call site (update.rs:294, grepped). No test hard-codes the old URL string separately (the update-command unit-test suite doesn't assert on the literal API string).Test plan
cargo build --workspaceclean (with the guest-wasm prereq already built)cargo test -p digstore-cli --lib update-- 22 passed, 1 ignored (alive_fetch_latest_releasenetwork test, ignored by design)cargo fmt --all -- --checkclean0.17.1->0.17.2,dig-client-wasm0.1.1->0.1.2(patch -- link/metadata fix, no behavior change)Co-Authored-By: Claude noreply@anthropic.com