Update op-challenger version for upgrade 16 to 1.5.1

[pauldowman]

op-challenger/v1.5.1 is a bug fix update that will be the required version for upgrade 16.

https://github.com/ethereum-optimism/optimism/releases/tag/op-challenger%2Fv1.5.1

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	14f273d
🔍 Latest deploy log	https://app.netlify.com/projects/docs-optimism/deploys/684c5dce9509400007ae4cb1
😎 Deploy Preview	https://deploy-preview-1660--docs-optimism.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

The upgrade instructions for chain operators have been updated to specify that the op-challenger component should now be upgraded from version 1.5.0 to version 1.5.1. No other changes were made to the upgrade process, technical details, or user instructions.

Possibly related PRs

• Update challenger info #1416: Updates documentation to specify the required version update of the op-challenger component for fault proof chains, directly related to upgrade instructions for the same component.
• Update pectra-changes.mdx #1492: Updates the required version of the op-challenger component in different upgrade notice files, reflecting version increments for the same binary in separate contexts.
• Draft U16 notice page #1618: Introduced the Upgrade 16 notice page and its content, which is directly modified by this PR.

Suggested reviewers

• bradleycamacho
• sbvegan

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5b51fd3 and 14f273d.

📒 Files selected for processing (1)

• pages/notices/upgrade-16.mdx (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with the following criteria: - First, check the frontmatter section at the top of the file: 1. For regular pages, ensure AL...

**/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

• First, check the frontmatter section at the top of the file:
  1. For regular pages, ensure ALL these fields are present and not empty:

  ---
  title: [non-empty]
  lang: [non-empty]
  description: [non-empty]
  topic: [non-empty]
  personas: [non-empty array]
  categories: [non-empty array]
  content_type: [valid type]
  ---

  2. For landing pages (index.mdx or files with ), only these fields are required:

  ---
  title: [non-empty]
  lang: [non-empty]
  description: [non-empty]
  topic: [non-empty]
  ---

  3. If any required fields are missing or empty, comment:
     'This file appears to be missing required metadata. Please check keywords.config.yaml for valid options and add the required fields manually. You can validate your changes by running:

  pnpm validate-metadata
  ```'

• 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:
  1. Use sentence case, capitalizing only the first word.
  2. 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.
  3. 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/upgrade-16.mdx

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Redirect rules - docs-optimism
• GitHub Check: Header rules - docs-optimism
• GitHub Check: Pages changed - docs-optimism

🔇 Additional comments (1)

pages/notices/upgrade-16.mdx (1)

40-40: Update is accurate

The bullet correctly instructs upgrading op-challenger to version v1.5.1 and links to the appropriate GitHub release tag.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[pauldowman]

closing as a duplicate of #1658