Skip to content

fix(digstore): correct Discord invite (imposter link -> official) - #18

Merged
MichaelTaylor3d merged 1 commit into
mainfrom
fix/discord-invite-imposter
Jul 12, 2026
Merged

fix(digstore): correct Discord invite (imposter link -> official)#18
MichaelTaylor3d merged 1 commit into
mainfrom
fix/discord-invite-imposter

Conversation

@MichaelTaylor3d

Copy link
Copy Markdown
Contributor

Summary

  • The vanity Discord invite https://discord.gg/dignetwork resolves to an imposter server, not the official DIG Network Discord.
  • Replaces every occurrence with the official invite https://discord.gg/v78aygUZt in README.md and the CLI branding constant DISCORD_URL (crates/digstore-cli/src/branding.rs).
  • Bumps [workspace.package].version 0.13.0 -> 0.13.1 (patch — docs/branding-only fix, no behavior change) and syncs the corresponding workspace-versioned crate entries (digstore-chain, digstore-chunker, digstore-cli, digstore-core, digstore-remote) in Cargo.lock.

Test plan

  • grep -rn "discord.gg/dignetwork" across the repo returns no matches.
  • New link https://discord.gg/v78aygUZt present in README.md and branding.rs.
  • Guest wasm built (cargo build -p digstore-guest --target wasm32-unknown-unknown --release) and cargo check -p digstore-cli passes locally with the bumped version + branding change.
  • CI green (fmt/clippy/tests/commitlint/version-gate).

Refs DIG-Network/dig_ecosystem#490

Co-Authored-By: Claude noreply@anthropic.com

The old vanity link https://discord.gg/dignetwork resolves to an
imposter server. Replace with the official invite in README.md and
the CLI branding constant (DISCORD_URL).

Co-Authored-By: Claude <noreply@anthropic.com>
@MichaelTaylor3d
MichaelTaylor3d merged commit 5820543 into main Jul 12, 2026
10 checks passed
@MichaelTaylor3d
MichaelTaylor3d deleted the fix/discord-invite-imposter branch July 12, 2026 22:32
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.

1 participant