Update monomer to v0.1.4 in testapp

[natebeauregard]

Summary by CodeRabbit

• New Features

  • Updated the monogen tool version for creating new Monomer applications from v0.1.4 to v0.1.5.

• Bug Fixes

  • Addressed a known vulnerability by updating the github.com/gin-gonic/gin dependency to v1.7.0.

• Documentation

  • Updated instructions for bootstrapping a new Monomer application to reflect the latest monogen version.

• Chores

  • Routine updates to various dependencies for compatibility and security improvements.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request includes updates to the go.mod file for the cmd/monogen/testapp module and corresponding documentation. The Go version has been upgraded from 1.22.0 to 1.23.0, and the github.com/polymerdao/monomer dependency has been updated from v0.1.3 to v0.1.4. Several other dependencies have been modified, including downgrades and replacements. Additionally, the documentation for creating a Monomer application has been revised to reflect the updated version of the monogen tool from v0.1.4 to v0.1.5.

Changes

File Path	Change Summary
cmd/monogen/testapp/go.mod	- Go version updated from 1.22.0 to 1.23.0 - github.com/polymerdao/monomer updated to v0.1.4 - github.com/btcsuite/btcd/btcec/v2 downgraded to v2.3.2 - github.com/crate-crypto/go-ipa updated to a specific commit - github.com/crate-crypto/go-kzg-4844 downgraded to v0.7.0 - github.com/ethereum/go-ethereum replaced with github.com/joshklop/op-geth - github.com/gin-gonic/gin updated to v1.7.0 due to a vulnerability - Other dependencies updated to specific versions.
docs/docs/build/create-an-app-with-monomer.md	- Command version updated from v0.1.4 to v0.1.5 for monogen.

Possibly related PRs

• Bump monogen patch version in docs to v0.1.2 #263: The documentation update in this PR reflects a change in the version of the monogen tool, which is directly related to the version updates in the go.mod file of the main PR.
• Update monomer to v0.1.3 in testapp #298: This PR updates the github.com/polymerdao/monomer dependency version in the go.mod file, which aligns with the version increment noted in the main PR.

Suggested reviewers

• joshklop

🐇 In the garden, hopping with glee,
Updated versions, oh so free!
Monomer's tools, now shine so bright,
With dependencies, all set right.
A leap for code, a joyful cheer,
In the world of Go, we persevere! 🌼

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 golangci-lint

level=warning msg="The linter 'exportloopref' is deprecated (since v1.60.2) due to: Since Go1.22 (loopvar) this linter is no longer relevant. Replaced by copyloopvar."

---

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?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.