Add release notes for Berachain – June 3, 2025#76
Conversation
WalkthroughA new changelog entry for June 3, 2025, was added, announcing the availability of deploying Global Nodes on the Berachain Mainnet. The update includes references to Berachain tooling and a Python quickstart tutorial, with a button linking to a detailed changelog page. The documentation configuration was updated to include these new pages. Changes
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (5)
✅ Files skipped from review due to trivial changes (3)
🚧 Files skipped from review as they are similar to previous changes (1)
🧰 Additional context used🪛 GitHub Check: Mintlify Validation - vale-spellcheckchangelog.mdx[warning] 9-9: changelog.mdx#L9 [warning] 9-9: changelog.mdx#L9 ⏰ Context from checks skipped due to timeout of 90000ms (1)
🔇 Additional comments (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![windsurf-bot[bot]](https://avatars.githubusercontent.com/in/1066231?s=60&v=4){kind=small}
| @@ -0,0 +1,3 @@ | |||
| title: "Chainstack updates: June 3 , 2025" | |||
There was a problem hiding this comment.
There is an extra space before the comma in the date in the title. Consider removing it for consistency.\n\nsuggestion\ntitle: "Chainstack updates: June 3, 2025"\n
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
changelog.mdx (1)
7-7: Inconsistent<Update>tag formatting
Add a trailing space before the closing bracket to match other entries.-<Update label="Chainstack updates: June 3, 2025" description=" by Vladimir"> +<Update label="Chainstack updates: June 3, 2025" description=" by Vladimir" >
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
changelog.mdx(1 hunks)changelog/chainstack-updates-june-3-2025.mdx(1 hunks)docs.json(1 hunks)
🧰 Additional context used
🪛 GitHub Check: Mintlify Validation - vale-spellcheck
changelog.mdx
[warning] 9-9: changelog.mdx#L9
Did you really mean 'Berachain'?
[warning] 9-9: changelog.mdx#L9
Did you really mean 'Mainnet'?
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: Mintlify Deployment
🔇 Additional comments (5)
changelog/chainstack-updates-june-3-2025.mdx (1)
3-3: Validate content labels and link targets.
Ensure the bold label Protocols aligns with naming conventions in other entries (singular vs. plural), and confirm that/docs/global-elastic-node,/docs/berachain-tooling, and/docs/berachain-dapp-tutorialresolve correctly in your documentation.docs.json (1)
2405-2405: Verify the new changelog page integrationThe entry
"changelog/chainstack-updates-june-3-2025"is added in the Release notes tab. Please confirm that:
- The file
changelog/chainstack-updates-june-3-2025.mdxexists and is properly located under your changelog directory.- The ordering remains in descending date order (newest first) in this list.
changelog.mdx (3)
9-9: Ignore Vale spellcheck warning
‘Berachain’ and ‘Mainnet’ are intentional and correct; the rule is a false positive.🧰 Tools
🪛 GitHub Check: Mintlify Validation - vale-spellcheck
[warning] 9-9: changelog.mdx#L9
Did you really mean 'Berachain'?
[warning] 9-9: changelog.mdx#L9
Did you really mean 'Mainnet'?
7-12: Approve new release note entry
The content, chronological placement, and internal links align with existing changelog conventions.🧰 Tools
🪛 GitHub Check: Mintlify Validation - vale-spellcheck
[warning] 9-9: changelog.mdx#L9
Did you really mean 'Berachain'?
[warning] 9-9: changelog.mdx#L9
Did you really mean 'Mainnet'?
11-11:Details
✅ Verification successful
Button link validity
The<Button>href points to/changelog/chainstack-updates-june-3-2025. Ensure the corresponding MDX file exists and is registered indocs.json.
🏁 Script executed:
#!/bin/bash # Verify the new changelog page is referenced in docs.json rg -R "chainstack-updates-june-3-2025.mdx" docs.jsonLength of output: 457
Let's correct the search and verify both the MDX file presence and its registration:
🏁 Script executed:
#!/bin/bash set -e echo "Locating docs.json file:" find . -type f -name "docs.json" echo echo "Searching for the changelog MDX file:" rg -g "*.mdx" "chainstack-updates-june-3-2025" echo echo "Verifying reference in docs.json:" grep -n "chainstack-updates-june-3-2025" docs.json || echo "No reference found in docs.json"Length of output: 537
To confirm the changelog page actually exists on disk, let’s locate the MDX file:
🏁 Script executed:
#!/bin/bash set -e echo "Checking for the changelog MDX file on disk:" find . -type f -name "chainstack-updates-june-3-2025.mdx" || echo "No MDX file found"Length of output: 212
Button link is valid
The filechangelog/chainstack-updates-june-3-2025.mdxexists under./changelogand is referenced indocs.json(line 2405). No further action needed.
| title: "Chainstack updates: June 3 , 2025" | ||
| --- |
There was a problem hiding this comment.
Fix front matter formatting and date spacing.
The file is missing the opening YAML delimiter and includes an extra space before the comma in the date, which will break front-matter parsing.
Apply this diff:
- title: "Chainstack updates: June 3 , 2025"
- ---
+ ---
+ title: "Chainstack updates: June 3, 2025"
+ ---📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| title: "Chainstack updates: June 3 , 2025" | |
| --- | |
| --- | |
| title: "Chainstack updates: June 3, 2025" | |
| --- |
🤖 Prompt for AI Agents
In changelog/chainstack-updates-june-3-2025.mdx at lines 1 to 2, the front
matter is missing the opening YAML delimiter and has an extra space before the
comma in the date. Add the opening triple-dash (---) at the start of the file
and remove the space before the comma in the date to fix the front matter
formatting and ensure proper parsing.
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
changelog.mdx(1 hunks)changelog/chainstack-updates-june-3-2025.mdx(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- changelog/chainstack-updates-june-3-2025.mdx
🧰 Additional context used
🪛 GitHub Check: Mintlify Validation - vale-spellcheck
changelog.mdx
[warning] 9-9: changelog.mdx#L9
Did you really mean 'Berachain'?
[warning] 9-9: changelog.mdx#L9
Did you really mean 'Mainnet'?
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: Mintlify Deployment
| <Update label="Chainstack updates: June 3, 2025" description=" by Vladimir"> | ||
|
|
||
| **Protocols**. Now, you can deploy [Global Nodes](/docs/global-elastic-node) for Berachain Mainnet. | ||
|
|
||
| <Button href="/changelog/chainstack-updates-june-3-2025">Read more</Button> | ||
| </Update> |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Release notes entry for June 3, 2025 is formatted and ordered correctly.
The new update matches the existing pattern—label, description, content, and button link are consistent. Please verify that the detailed changelog page chainstack-updates-june-3-2025.mdx is present and that docs.json has been updated to include this entry.
🏁 Script executed:
#!/bin/bash
# Verify the new detailed changelog page exists
fd --glob 'chainstack-updates-june-3-2025.mdx'
# Verify docs.json references the new entry
rg '"chainstack-updates-june-3-2025"' docs.jsonLength of output: 141
Missing docs.json entry for the new changelog page
- The detailed changelog page
changelog/chainstack-updates-june-3-2025.mdxis present. docs.jsondoes not include a reference to"chainstack-updates-june-3-2025".
Please add the new entry to docs.json, for example:
{
// existing entries...
+ "chainstack-updates-june-3-2025": {
+ "title": "Chainstack updates: June 3, 2025",
+ "path": "/changelog/chainstack-updates-june-3-2025"
+ }
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| <Update label="Chainstack updates: June 3, 2025" description=" by Vladimir"> | |
| **Protocols**. Now, you can deploy [Global Nodes](/docs/global-elastic-node) for Berachain Mainnet. | |
| <Button href="/changelog/chainstack-updates-june-3-2025">Read more</Button> | |
| </Update> | |
| { | |
| // existing entries... | |
| "chainstack-updates-june-3-2025": { | |
| "title": "Chainstack updates: June 3, 2025", | |
| "path": "/changelog/chainstack-updates-june-3-2025" | |
| } | |
| } |
🧰 Tools
🪛 GitHub Check: Mintlify Validation - vale-spellcheck
[warning] 9-9: changelog.mdx#L9
Did you really mean 'Berachain'?
[warning] 9-9: changelog.mdx#L9
Did you really mean 'Mainnet'?
🤖 Prompt for AI Agents
In changelog.mdx around lines 7 to 12, the new detailed changelog page
chainstack-updates-june-3-2025.mdx exists, but docs.json does not reference it.
To fix this, open docs.json and add an entry for
"chainstack-updates-june-3-2025" following the existing pattern for changelog
pages, ensuring the new changelog is properly linked and discoverable.
3 participants
Summary
Summary by CodeRabbit