Conversation
Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
The developer blog stops at T7 even though the protocol docs cover T8, T9, and T10. Add one network-upgrade post for each release, with integration guidance and links to the existing upgrade references and specifications.
The posts follow the existing blog format and Tempo writing guidelines. Dates match the documented mainnet activations (July 30, August 6, and August 21, 2026), following the T7 post's convention. These are retrospective posts; node guidance links to the current release table instead of recommending an obsolete binary.
Validation: Type checking passed. All three posts pass the existing blog renderer with valid metadata and internal page/anchor links. The repository internal-anchor check also passed.
Full build and browser page validation remain blocked: Vocs cannot fetch
https://api.tempo.xyz/openapi.jsonfrom this sandbox (connection timeout). The same dependency blocks the dev server. No site configuration was changed to bypass it. This PR is a draft pending review and full preview validation; nothing has been published.Prompted by: @snario