[docs-agent] Remove Sonic Blaze testnet from docs (post-cutoff cleanup)#1383
Merged
Conversation
Sonic Blaze was sunset by Sonic Labs on May 1, 2026. PR #1347 (merged 2026-06-03) added the deprecation notice page with a June 12, 2026 cutoff. This is the post-cutoff partial-deprecation cleanup: - src/openrpc/chains/sonic/sonic.yaml: drop sonic-blaze server entry - src/openrpc/alchemy/{trace,debug}/*.yaml: drop sonic-blaze server entry - content/api-reference/node-api/node-supported-chains.mdx: drop the Sonic Blaze row - content/api-reference/sonic/sonic-api-quickstart.mdx: remove the <Warning> callout (cutoff has passed) - content/api-reference/sonic/sonic-blaze-deprecation-notice.mdx: flip to past tense Sonic Mainnet and Sonic Testnet stay. The deprecation notice page is kept in nav so old links land on migration info. Refs DOCS-116
🔗 Preview Mode
|
mihaiciuciu3410
approved these changes
Jun 15, 2026
SahilAujla
approved these changes
Jun 15, 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
4 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.
Summary
Post-cutoff cleanup for the Sonic Blaze testnet deprecation. Sonic Blaze was sunset by Sonic Labs on May 1, 2026; PR #1347 (merged 2026-06-03) added the deprecation notice page with a June 12, 2026 cutoff. That cutoff has now passed (today is 2026-06-15), so this PR removes the lingering live references.
Partial deprecation — Sonic Mainnet and Sonic Testnet stay.
Changes
src/openrpc/chains/sonic/sonic.yaml— drop thesonic-blazeserver entry from the Sonic chain spec.src/openrpc/alchemy/trace/trace.yaml— drop thesonic-blazeserver entry.src/openrpc/alchemy/debug/debug.yaml— drop thesonic-blazeserver entry.content/api-reference/node-api/node-supported-chains.mdx— drop the Sonic Blaze row from the supported-chains table.content/api-reference/sonic/sonic-api-quickstart.mdx— remove the<Warning>callout (no longer "ending June 12", it has ended).content/api-reference/sonic/sonic-blaze-deprecation-notice.mdx— flip from future tense ("will fully deprecate on June 12") to past tense ("ended on June 12").Preserved
content/api-reference/sonic/sonic-blaze-deprecation-notice.mdx(the page itself) and its nav entry incontent/docs.ymlare kept so that users with stale/docs/reference/sonic-blaze-deprecation-noticelinks still land on migration info. No new redirects required — the deprecation notice page already exists at a stable URL and no oldsonic-blazeURLs exist incontent/redirects.yml.Verification
Final sweep:
grep -rn -i "sonic-blaze\|Sonic Blaze\|SONIC_BLAZE" content/ src/returns only the kept deprecation notice page and itsdocs.ymlnav entry.Linear
DOCS-116 — Chain deprecation: SONIC_BLAZE (partial dep, post-cutoff removal)