Skip to content

wardend: prepare release v0.6.5#1633

Merged
Pitasi merged 3 commits intomainfrom
prepare-release-0.6.5
Jul 23, 2025
Merged

wardend: prepare release v0.6.5#1633
Pitasi merged 3 commits intomainfrom
prepare-release-0.6.5

Conversation

@Pitasi
Copy link
Contributor

@Pitasi Pitasi commented Jul 23, 2025

This PR prepares wardend for v0.6.5.

It adds the necessary x/async migration for creating the new plugin metrics entries in the db.

@Pitasi Pitasi requested a review from a team as a code owner July 23, 2025 10:03
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 23, 2025

📝 Walkthrough

Walkthrough

This change introduces an upgrade handler for version 0.6.5, updates the changelog and dependency on the Cosmos SDK, and adds a migration for the x/async module to initialize plugin metrics. The consensus version of the x/async module is incremented, and migration registration logic is updated to handle the new version.

Changes

File(s) Change Summary
CHANGELOG.md Added unreleased and 0.6.5 sections, documented consensus breaking changes, features, and restructured entries.
go.mod Updated github.com/cosmos/cosmos-sdk dependency from v0.53.2 to v0.53.3.
warden/app/app.go Added upgrade handler for "v0.6.5" to run module migrations on upgrade.
warden/x/async/keeper/migrations.go Introduced Migrate3to4 method to initialize plugin metrics for all plugins in migration.
warden/x/async/module/module.go Registered migration from version 3 to 4, updated consensus version to 4.

Sequence Diagram(s)

sequenceDiagram
    participant UpgradeKeeper
    participant App
    participant ModuleManager
    participant AsyncModule

    UpgradeKeeper->>App: Trigger upgrade "v0.6.5"
    App->>ModuleManager: RunMigrations(ctx, configurator, versionMap)
    ModuleManager->>AsyncModule: Migrate3to4(ctx)
    AsyncModule->>AsyncModule: Initialize plugin metrics for all plugins
    AsyncModule-->>ModuleManager: Migration complete
    ModuleManager-->>App: Updated versionMap, error (if any)
    App-->>UpgradeKeeper: Migration result
Loading

Estimated code review effort

2 (~15 minutes)

Possibly related PRs

Suggested labels

wardenkms, x-warden


📜 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 7167ed4 and 238d236.

📒 Files selected for processing (3)
  • warden/app/app.go (3 hunks)
  • warden/x/async/keeper/migrations.go (2 hunks)
  • warden/x/async/module/module.go (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • warden/app/app.go
  • warden/x/async/module/module.go
  • warden/x/async/keeper/migrations.go
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
  • GitHub Check: lint
  • GitHub Check: lint
  • GitHub Check: test
  • GitHub Check: lint
  • GitHub Check: test
  • GitHub Check: Analyze (go)
  • GitHub Check: Analyze (javascript-typescript)
✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f4b79ac and 96fc168.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (5)
  • CHANGELOG.md (1 hunks)
  • go.mod (1 hunks)
  • warden/app/app.go (3 hunks)
  • warden/x/async/keeper/migrations.go (2 hunks)
  • warden/x/async/module/module.go (2 hunks)
📓 Path-based instructions (1)
**/*.md

⚙️ CodeRabbit Configuration File

**/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

Files:

  • CHANGELOG.md
🧠 Learnings (3)
warden/app/app.go (1)

Learnt from: backsapc
PR: #975
File: warden/app/app.go:562-562
Timestamp: 2024-11-02T10:21:03.096Z
Learning: In warden/app/app.go, suggestions to handle errors from ParamsKeeper.GetSubspace() may be considered out of scope.

warden/x/async/keeper/migrations.go (1)

Learnt from: backsapc
PR: #975
File: warden/app/app.go:562-562
Timestamp: 2024-11-02T10:21:03.096Z
Learning: In warden/app/app.go, suggestions to handle errors from ParamsKeeper.GetSubspace() may be considered out of scope.

CHANGELOG.md (1)

Learnt from: backsapc
PR: #810
File: keychain-sdk/internal/tracker/status_tracker.go:0-0
Timestamp: 2024-10-24T13:03:19.344Z
Learning: The MarkProcessed method has been removed from keychain-sdk/internal/tracker/status_tracker.go in the Go codebase, as it is no longer needed.

🧰 Additional context used
📓 Path-based instructions (1)
**/*.md

⚙️ CodeRabbit Configuration File

**/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

Files:

  • CHANGELOG.md
🧠 Learnings (3)
warden/app/app.go (1)

Learnt from: backsapc
PR: #975
File: warden/app/app.go:562-562
Timestamp: 2024-11-02T10:21:03.096Z
Learning: In warden/app/app.go, suggestions to handle errors from ParamsKeeper.GetSubspace() may be considered out of scope.

warden/x/async/keeper/migrations.go (1)

Learnt from: backsapc
PR: #975
File: warden/app/app.go:562-562
Timestamp: 2024-11-02T10:21:03.096Z
Learning: In warden/app/app.go, suggestions to handle errors from ParamsKeeper.GetSubspace() may be considered out of scope.

CHANGELOG.md (1)

Learnt from: backsapc
PR: #810
File: keychain-sdk/internal/tracker/status_tracker.go:0-0
Timestamp: 2024-10-24T13:03:19.344Z
Learning: The MarkProcessed method has been removed from keychain-sdk/internal/tracker/status_tracker.go in the Go codebase, as it is no longer needed.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)
  • GitHub Check: lint
  • GitHub Check: test
  • GitHub Check: lint
  • GitHub Check: test
  • GitHub Check: test
  • GitHub Check: lint
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Analyze (go)
🔇 Additional comments (9)
go.mod (1)

59-59: LGTM! Cosmos SDK dependency update is correct.

The version bump from v0.53.2 to v0.53.3 aligns with the changelog entry and follows proper semantic versioning.

warden/app/app.go (3)

4-4: LGTM! Import addition is appropriate.

The context import is correctly added to support the upgrade handler function signature.


20-20: LGTM! Import addition is appropriate.

The upgradetypes import is correctly added to support the upgrade handler function signature.


546-548: LGTM! Upgrade handler implementation follows best practices.

The v0.6.5 upgrade handler correctly runs module migrations using the module manager, which will trigger the x/async migration from version 3 to 4 that initializes plugin metrics.

warden/x/async/module/module.go (1)

160-160: LGTM! Consensus version correctly updated.

The consensus version is properly incremented to 4 to reflect the new migration that initializes plugin metrics.

warden/x/async/keeper/migrations.go (2)

16-19: LGTM! Import additions are appropriate.

The imports for Cosmos SDK types and v1beta1 plugin types are correctly added to support the migration logic.


31-40: LGTM! Migration implementation is correct.

The Migrate3to4 method properly:

  • Iterates through all existing plugins using Walk
  • Initializes new plugin metrics for each plugin
  • Handles errors appropriately by stopping iteration and returning the error
  • Uses the correct plugin ID for metrics initialization

This will ensure all existing plugins have metrics initialized during the v0.6.5 upgrade.

CHANGELOG.md (2)

45-47: LGTM! Unreleased sections properly added.

The new unreleased sections for features and bug fixes follow the established changelog format and provide structure for future changes.


49-63: LGTM! Release documentation is comprehensive and accurate.

The v0.6.5 release entry properly documents:

  • Consensus breaking changes including plugin metrics addition
  • Feature improvements like image quality enhancements
  • The Cosmos SDK version bump to v0.53.3
  • All changes align with the actual code modifications in this PR

@Pitasi Pitasi force-pushed the prepare-release-0.6.5 branch from 96fc168 to 7167ed4 Compare July 23, 2025 10:07
@vercel
Copy link

vercel bot commented Jul 23, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
warden-help-center ⬜️ Ignored (Inspect) Visit Preview Jul 23, 2025 11:17am

@Pitasi Pitasi force-pushed the prepare-release-0.6.5 branch from 7167ed4 to 238d236 Compare July 23, 2025 11:17
@Pitasi Pitasi merged commit c971f0c into main Jul 23, 2025
23 checks passed
@Pitasi Pitasi deleted the prepare-release-0.6.5 branch July 23, 2025 11:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant