Skip to content

Add EVM v0.7 upgrade guide#311

Open
evanorti wants to merge 1 commit intomainfrom
evm-upgrade-7
Open

Add EVM v0.7 upgrade guide#311
evanorti wants to merge 1 commit intomainfrom
evm-upgrade-7

Conversation

@evanorti
Copy link
Copy Markdown
Contributor

Placeholder for evm v0.7 upgrade guide

[] Upgrade guide will need to be added to the blank pages in this PR (in evm/latest and copied to evm/next)

@mintlify
Copy link
Copy Markdown

mintlify Bot commented Apr 28, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
cosmos-docs 🟢 Ready View Preview Apr 28, 2026, 3:27 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 28, 2026

Greptile Summary

This PR adds placeholder migration guide pages for EVM v0.6→v0.7 in both evm/latest and evm/next, and updates docs.json to promote the new guide to the top-level Migrations entry while moving the v0.5→v0.6 guide into the "Previous Versions" collapsed group.

  • Blank pages in production: Both migration-v0.6-to-v0.7.mdx files contain only a frontmatter title with no body. The PR description acknowledges the content is missing, but as-is these pages will be live and empty for site visitors navigating to the migration guide.

Confidence Score: 3/5

Not safe to merge until migration guide content is added — blank pages will be visible to users on the live site.

The docs.json navigation changes are correct and well-structured. However, both new MDX files are intentionally empty placeholders that will render as blank pages in production, which is a P1 user-facing issue. The PR description explicitly flags this as incomplete work.

evm/latest/documentation/migrations/migration-v0.6-to-v0.7.mdx and evm/next/documentation/migrations/migration-v0.6-to-v0.7.mdx — both need actual migration guide content before this is suitable to merge.

Important Files Changed

Filename Overview
docs.json Correctly promotes migration-v0.6-to-v0.7 as the top-level migration entry in both evm/latest and evm/next, and moves migration-v0.5-to-v0.6 into the "Previous Versions" collapsed group — structure is consistent between both version trees.
evm/latest/documentation/migrations/migration-v0.6-to-v0.7.mdx Placeholder file with only a frontmatter title and no body content; will render as a blank page for site visitors, and is also missing a trailing newline.
evm/next/documentation/migrations/migration-v0.6-to-v0.7.mdx Identical placeholder file synced from latest/; same empty-content and missing-newline issues apply.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Migrations nav group\n(evm/latest & evm/next)"]
    A --> B["migration-v0.6-to-v0.7 ⬅ NEW (top-level)"]
    A --> C["Previous Versions (collapsed)"]
    C --> D["migration-v0.5-to-v0.6 ⬅ moved here"]
    C --> E["migration-v0.4-to-v0.5"]
    C --> F["migration-v0.3-to-v0.4"]
    C --> G["erc20-precompiles-migration"]

    style B fill:#f9a,stroke:#c66
    style D fill:#adf,stroke:#66c
Loading

Reviews (1): Last reviewed commit: "0.7 upgrade guide" | Re-trigger Greptile

Comment on lines +1 to +3
---
title: "Migration: v0.6.0 to v0.7.0"
--- No newline at end of file
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Empty placeholder page will be visible to users

This file is published to the live docs site with only a title and no content. Visitors navigating to the v0.6→v0.7 migration guide will see a completely blank page. If the content won't be ready before this PR merges, consider adding a brief notice (e.g., "Coming soon" or a draft warning) so the page is not silently empty in production.

@@ -0,0 +1,3 @@
---
title: "Migration: v0.6.0 to v0.7.0"
--- No newline at end of file
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Missing newline at end of file

The file is missing a trailing newline (shown as \ No newline at end of file in the diff). This applies to both evm/latest and evm/next copies.

Suggested change
---
---
title: "Migration: v0.6.0 to v0.7.0"
---

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