Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create the (empty) umber-rc2 upgrade. #2069

Merged
merged 5 commits into from
Jul 9, 2024
Merged

Create the (empty) umber-rc2 upgrade. #2069

merged 5 commits into from
Jul 9, 2024

Conversation

SpicyLemon
Copy link
Contributor

@SpicyLemon SpicyLemon commented Jul 8, 2024

Description

This PR creates an empty umber-rc2 upgrade.

There is nothing involved in this upgrade, it just gives us a coordinated way to fix the app hash problems.

Of course, it's very possible that something gets added to it before we do it, but for now, it's empty.


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md)
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Wrote unit and integration tests
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/)
  • Added relevant godoc comments.
  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Re-reviewed Files changed in the Github PR explorer
  • Review Codecov Report in the comment section below once CI passes

Summary by CodeRabbit

  • New Features

    • Added a new upgrade entry for v1.19.0-rc3 and an empty upgrade for umber-rc2.
  • Dependency Updates

    • Updated github.com/hashicorp/go-getter to a newer version.
  • Tests

    • Added a test for the umber-rc2 upgrade process.

@SpicyLemon SpicyLemon requested a review from a team as a code owner July 8, 2024 20:18
Copy link
Contributor

coderabbitai bot commented Jul 8, 2024

Warning

Rate limit exceeded

@iramiller has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 1 minutes and 24 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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.

Commits

Files that changed from the base of the PR and between 5ebda57 and 24fb13c.

Walkthrough

Recent updates include adding an empty upgrade entry for umber-rc2, updating version numbers, and adding a new upgrade for v1.19.0-rc3. Additionally, a new test function named TestUmberRC2() is added to verify the upgrade process. The changes also involve updating all proto links in the spec docs to point to v1.19.0 versions.

Changes

File Summary
CHANGELOG.md Updated with an empty upgrade for umber-rc2 and updated proto links to v1.19.0 version.
app/upgrades.go Updated version comments and added a new upgrade entry for v1.19.0-rc3.
app/upgrades_test.go Added TestUmberRC2() function to test the upgrade for umber-rc2.

Poem

A change so slight, yet shining bright,
With versions new in lines we write.
The tests now check what's set to be,
From umber-rc2 to v1.19.0, we see.
Our code, a journey, never ends,
With each upgrade, a message it sends.
🐇✨🔧


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
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

Taztingo
Taztingo previously approved these changes Jul 8, 2024
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: 0

Outside diff range and nitpick comments (1)
CHANGELOG.md (1)

42-42: Address markdown lint issue: Change dash to asterisk for unordered list style.

To maintain consistency with the unordered list style used in the rest of the document, change the dash to an asterisk.

- * Add the (empty) `umber-rc2` upgrade [#2069](https://github.com/provenance-io/provenance/pull/2069).
+ * Add the (empty) `umber-rc2` upgrade [#2069](https://github.com/provenance-io/provenance/pull/2069).
Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 48133a0 and 8d55a0a.

Files selected for processing (3)
  • CHANGELOG.md (1 hunks)
  • app/upgrades.go (2 hunks)
  • app/upgrades_test.go (1 hunks)
Files skipped from review due to trivial changes (1)
  • app/upgrades.go
Additional context used
Markdownlint
CHANGELOG.md

46-46: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)

Additional comments not posted (1)
app/upgrades_test.go (1)

405-415: LGTM! Consider adding more comprehensive tests.

The function correctly verifies the umber-rc2 upgrade entry. However, consider adding more comprehensive tests to cover future changes.

@SpicyLemon SpicyLemon enabled auto-merge (squash) July 8, 2024 20:32
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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8d55a0a and 5ebda57.

Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • CHANGELOG.md

@SpicyLemon SpicyLemon merged commit d8f0051 into main Jul 9, 2024
31 checks passed
@SpicyLemon SpicyLemon deleted the dwedul/umber-rc2 branch July 9, 2024 18:22
SpicyLemon added a commit that referenced this pull request Jul 11, 2024
* Add the umber-rc2 upgrade (which does nothing).

* Add changelog entry.
iramiller added a commit that referenced this pull request Jul 11, 2024
* Add the umber-rc2 upgrade (which does nothing).

* Add changelog entry.

Co-authored-by: Ira Miller <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants