adding the release tags and binaries #1353
Conversation
✅ Deploy Preview for docs-optimism ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Warning Rate limit exceeded@sbvegan has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 6 minutes and 18 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe document has been significantly revised to shift focus from chain operators to node operators regarding the Ethereum Pectra upgrade. The section originally titled "For chain operators" has been renamed to "For node operators," emphasizing the need for node operators to upgrade before activation dates, with specific steps outlined for them. The steps for upgrading have been consolidated under the new node operator section, and a warning callout has been added for full node operators running Possibly related PRs
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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
Documentation and Community
|
![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)
pages/notices/pectra-changes.mdx (1)
57-58: Fix grammar and formatting issues.There are a few issues in this section:
- Double verb usage: "you're are"
- Missing space after period in "features.We"
-If you're are running a fault proof enabled chain +If you are running a fault proof enabled chain-features.We +features. We🧰 Tools
🪛 LanguageTool
[uncategorized] ~57-~57: “you’re” (you are) seems less likely than “you”.
Context: ...ctional after the L1 Pectra upgrade. If you're are running a fault proof enabled chain...(AI_HYDRA_LEO_CP_YOUARE_YOU)
[uncategorized] ~57-~57: Possible wrong verb form detected. Did you mean “been” or “being”?
Context: ... after the L1 Pectra upgrade. If you're are running a fault proof enabled chain, yo...(BE_WITH_WRONG_VERB_FORM)
[style] ~58-~58: Consider using a more formal alternative.
Context: ...ncludes these features. We will provide more information as engineering work wraps up. We are tr...(MORE_INFO)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
pages/notices/pectra-changes.mdx(3 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with ...
**/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:
- Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
- Avoid gender-specific language and use the imperative form.
- Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
- Ensure proper nouns are capitalized in sentences.
- Apply the Oxford comma.
- Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
- Use correct spelling and grammar at all times (IMPORTANT).
- For H1, H2, and H3 headers:
- Use sentence case, capitalizing only the first word.
- Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
- Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
- Flag any headers that seem to inconsistently apply these rules for manual review.
- When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
"
pages/notices/pectra-changes.mdx
🪛 LanguageTool
pages/notices/pectra-changes.mdx
[duplication] ~50-~50: Possible typo: you repeated a word.
Context: ...test release. * op-node at v1.11.0 * op-geth at v1.101500.0 ## For chain operato...
(ENGLISH_WORD_REPEAT_RULE)
[uncategorized] ~57-~57: “you’re” (you are) seems less likely than “you”.
Context: ...ctional after the L1 Pectra upgrade. If you're are running a fault proof enabled chain...
(AI_HYDRA_LEO_CP_YOUARE_YOU)
[uncategorized] ~57-~57: Possible wrong verb form detected. Did you mean “been” or “being”?
Context: ... after the L1 Pectra upgrade. If you're are running a fault proof enabled chain, yo...
(BE_WITH_WRONG_VERB_FORM)
[style] ~58-~58: Consider using a more formal alternative.
Context: ...ncludes these features. We will provide more information as engineering work wraps up. We are tr...
(MORE_INFO)
⏰ Context from checks skipped due to timeout of 90000ms (4)
- GitHub Check: Redirect rules - docs-optimism
- GitHub Check: Header rules - docs-optimism
- GitHub Check: Pages changed - docs-optimism
- GitHub Check: pr-workflow
There was a problem hiding this comment.
Actionable comments posted: 3
♻️ Duplicate comments (1)
pages/notices/pectra-changes.mdx (1)
54-54:⚠️ Potential issueAdd missing version link for op-node.
The version link for
op-node v1.11.0is empty. Please add the correct GitHub release URL.🧰 Tools
🪛 LanguageTool
[duplication] ~54-~54: Possible typo: you repeated a word.
Context: ...test release. *op-nodeatv1.11.0*op-gethat [v1.101500.0](https://github.com/ethe...(ENGLISH_WORD_REPEAT_RULE)
🧹 Nitpick comments (1)
pages/notices/pectra-changes.mdx (1)
61-61: Consider using a more robust anchor reference.The current anchor reference
#update-to-the-latest-releasemight break if the heading text changes. Consider adding an explicit ID to the heading for a more stable reference.-[Node Operator section](#update-to-the-latest-release) +[Node Operator section](#node-operator-update)And add an ID to the corresponding heading:
-### Update to the latest release +### Update to the latest release {#node-operator-update}
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
pages/notices/pectra-changes.mdx(4 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with ...
**/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:
- Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
- Avoid gender-specific language and use the imperative form.
- Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
- Ensure proper nouns are capitalized in sentences.
- Apply the Oxford comma.
- Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
- Use correct spelling and grammar at all times (IMPORTANT).
- For H1, H2, and H3 headers:
- Use sentence case, capitalizing only the first word.
- Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
- Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
- Flag any headers that seem to inconsistently apply these rules for manual review.
- When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
"
pages/notices/pectra-changes.mdx
🪛 LanguageTool
pages/notices/pectra-changes.mdx
[uncategorized] ~13-~13: Possible wrong verb form detected. Did you mean “been” or “being”?
Context: ... after the L1 Pectra upgrade. If you're are running a fault proof enabled chain, yo...
(BE_WITH_WRONG_VERB_FORM)
[style] ~14-~14: Consider using a more formal alternative.
Context: ...ncludes these features. We will provide more information as engineering work wraps up. We are tr...
(MORE_INFO)
[duplication] ~54-~54: Possible typo: you repeated a word.
Context: ...test release. * op-node at v1.11.0 * op-geth at [v1.101500.0](https://github.com/ethe...
(ENGLISH_WORD_REPEAT_RULE)
⏰ Context from checks skipped due to timeout of 90000ms (4)
- GitHub Check: pr-workflow
- GitHub Check: Redirect rules - docs-optimism
- GitHub Check: Header rules - docs-optimism
- GitHub Check: Pages changed - docs-optimism
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Updating the notice page with the new release tags and will update this PR with the release notes once they're available