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

Update mainnet and testnet images for v6.0.0 development #2053

Merged
merged 1 commit into from
Aug 7, 2024

Conversation

roy-dydx
Copy link
Contributor

@roy-dydx roy-dydx commented Aug 7, 2024

Changelist

Images include previous version v5.2.0 and current commit as v6.0.0

Test Plan

[Describe how this PR was tested (if applicable)]

Author/Reviewer Checklist

  • If this PR has changes that result in a different app state given the same prior state and transaction list, manually add the state-breaking label.
  • If the PR has breaking postgres changes to the indexer add the indexer-postgres-breaking label.
  • If this PR isn't state-breaking but has changes that modify behavior in PrepareProposal or ProcessProposal, manually add the label proposal-breaking.
  • If this PR is one of many that implement a specific feature, manually label them all feature:[feature-name].
  • If you wish to for mergify-bot to automatically create a PR to backport your change to a release branch, manually add the label backport/[branch-name].
  • Manually add any of the following labels: refactor, chore, bug.

Summary by CodeRabbit

  • New Features

    • Updated version mappings to reference new software versions (v5.2.0 and v6.0.0), ensuring access to the latest features and improvements.
  • Bug Fixes

    • Improved versioning structure to maintain compatibility with the latest software releases.

Copy link
Contributor

coderabbitai bot commented Aug 7, 2024

Walkthrough

The recent changes involve updating version references in several shell scripts related to the dydxprotocold package. Specifically, the version mappings have been changed from v5.1.0 to v5.2.0 in the mainnet and testnet scripts, while transitioning to a new major version v6.0.0 in the directory variables. These updates reflect enhancements and improvements in the software, ensuring proper retrieval of the latest versions during execution.

Changes

Files Change Summary
protocol/testing/mainnet/mainnet.sh Updated version mapping from v5.1.0 to v5.2.0.
protocol/testing/mainnet/vars.sh Updated CURRENT_VERSION_DIR from v5.1.0 to v6.0.0.
protocol/testing/testnet/testnet.sh Updated version mapping from v5.1.0 to v5.2.0.
protocol/testing/testnet/vars.sh Updated CURRENT_VERSION_DIR from v5.2.0 to v6.0.0.

Poem

🐇 In the meadow where the code does play,
New versions hop in a joyful display.
From five point one, to six they leap,
A dance of changes, a promise to keep.
With every update, the software grows bright,
A rabbit's delight in the coding night! 🌙✨


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

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 73b04dc and 8c3f86b.

Files selected for processing (4)
  • protocol/testing/mainnet/mainnet.sh (1 hunks)
  • protocol/testing/mainnet/vars.sh (1 hunks)
  • protocol/testing/testnet/testnet.sh (1 hunks)
  • protocol/testing/testnet/vars.sh (1 hunks)
Files skipped from review due to trivial changes (2)
  • protocol/testing/mainnet/mainnet.sh
  • protocol/testing/testnet/testnet.sh
Additional context used
Shellcheck
protocol/testing/mainnet/vars.sh

[warning] 4-4: CURRENT_VERSION_DIR appears unused. Verify use (or export if used externally).

(SC2034)

protocol/testing/testnet/vars.sh

[warning] 4-4: CURRENT_VERSION_DIR appears unused. Verify use (or export if used externally).

(SC2034)

Additional comments not posted (2)
protocol/testing/mainnet/vars.sh (1)

4-4: Verify usage of CURRENT_VERSION_DIR.

The variable CURRENT_VERSION_DIR is updated to "v6.0.0", but it appears unused within this script. Ensure that it is used elsewhere or consider exporting it if needed.

Verification successful

CURRENT_VERSION_DIR is used in other scripts.

The variable CURRENT_VERSION_DIR is indeed used in other scripts within the codebase. It is referenced in both testnet.sh and mainnet.sh scripts to construct the path for current_version_path. Thus, the update to "v6.0.0" is valid and utilized.

  • protocol/testing/testnet/testnet.sh
  • protocol/testing/mainnet/mainnet.sh
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of `CURRENT_VERSION_DIR` in the codebase.

# Test: Search for the usage of `CURRENT_VERSION_DIR`. Expect: Occurrences of the variable in other scripts or files.
rg --type shell 'CURRENT_VERSION_DIR'

Length of output: 67


Script:

#!/bin/bash
# Description: Verify the usage of `CURRENT_VERSION_DIR` in the codebase.

# Test: Search for the usage of `CURRENT_VERSION_DIR` in all files.
rg 'CURRENT_VERSION_DIR'

Length of output: 376

Tools
Shellcheck

[warning] 4-4: CURRENT_VERSION_DIR appears unused. Verify use (or export if used externally).

(SC2034)

protocol/testing/testnet/vars.sh (1)

4-4: Verify usage of CURRENT_VERSION_DIR.

The variable CURRENT_VERSION_DIR is updated to "v6.0.0", but it appears unused within this script. Ensure that it is used elsewhere or consider exporting it if needed.

Verification successful

"""

"""


CURRENT_VERSION_DIR is used in other scripts.

The variable CURRENT_VERSION_DIR is indeed used in other parts of the codebase, specifically in the testnet.sh and mainnet.sh scripts. This confirms that the variable is not unused and plays a role in setting the current_version_path.

  • protocol/testing/testnet/testnet.sh: Used to construct the current_version_path.
  • protocol/testing/mainnet/mainnet.sh: Similarly used to construct the current_version_path.

No changes are needed regarding the usage of this variable.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of `CURRENT_VERSION_DIR` in the codebase.

# Test: Search for the usage of `CURRENT_VERSION_DIR`. Expect: Occurrences of the variable in other scripts or files.
rg --type shell 'CURRENT_VERSION_DIR'

Length of output: 67


Script:

#!/bin/bash
# Corrected command to search for the usage of `CURRENT_VERSION_DIR` in the codebase.
rg 'CURRENT_VERSION_DIR'

Length of output: 376

Tools
Shellcheck

[warning] 4-4: CURRENT_VERSION_DIR appears unused. Verify use (or export if used externally).

(SC2034)

@roy-dydx roy-dydx merged commit 6f39469 into main Aug 7, 2024
17 checks passed
@roy-dydx roy-dydx deleted the roy/imagesv6 branch August 7, 2024 18:39
@roy-dydx
Copy link
Contributor Author

roy-dydx commented Aug 7, 2024

https://github.com/Mergifyio backport release/protocol/v6.x

Copy link
Contributor

mergify bot commented Aug 7, 2024

backport release/protocol/v6.x

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Aug 7, 2024
roy-dydx added a commit that referenced this pull request Aug 7, 2024
@coderabbitai coderabbitai bot mentioned this pull request Sep 27, 2024
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants