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

release: updated to 1.4.0-dev.3 #2190

Merged
merged 1 commit into from
Oct 1, 2024
Merged

Conversation

QuantumExplorer
Copy link
Member

@QuantumExplorer QuantumExplorer commented Oct 1, 2024

Issue being fixed or feature implemented

What was done?

Bumped packages version.

How Has This Been Tested?

Breaking Changes

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
  • I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

Summary by CodeRabbit

  • New Features

    • Incremented version numbers across multiple packages to 1.4.0-dev.3, indicating a new development iteration.
  • Bug Fixes

    • No specific bug fixes were noted in this release.
  • Chores

    • Maintained consistency in dependencies and package configuration across various packages without introducing new functionalities.

Copy link
Contributor

coderabbitai bot commented Oct 1, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates the version numbers across multiple packages in the @dashevo ecosystem from 1.4.0-dev.2 to 1.4.0-dev.3. This change applies to various components, including package.json and Cargo.toml files, without altering dependencies, scripts, or functionality. The updates reflect an ongoing development cycle, ensuring consistency in versioning across the project.

Changes

File(s) Change Summary
package.json (multiple packages) Version updated from 1.4.0-dev.2 to 1.4.0-dev.3. No other changes made.
Cargo.toml (multiple packages) Version updated from 1.4.0-dev.2 to 1.4.0-dev.3. No other changes made.
Cargo.toml for rs-dpp Version updated; dependencies updated: bincode, once_cell, tokio, and serde.
Cargo.toml for rs-drive-abci Version updated; dependencies updated: bincode, tokio, tracing-subscriber, tenderdash-abci.
Cargo.toml for rs-drive-proof-verifier Version updated; dependencies updated: bincode, tenderdash-abci.
Cargo.toml for rs-drive Version updated; authors list corrected; new features added to dpp.
Cargo.toml for strategy-tests Version updated; added rocksdb dependency under [dev-dependencies].
Cargo.toml for simple-signer Version updated; dependencies updated: bincode, dashcore-rpc, dpp.
Cargo.toml for withdrawals-contract Version updated; no changes to dependencies.

Possibly related PRs

Suggested reviewers

  • lklimek

🐇 In the meadow, hopping with glee,
Version numbers rise, as bright as can be!
From 2 to 3, we bounce and we play,
New updates are here, hip-hip-hooray!
With packages aligned, all tidy and neat,
Let's celebrate progress, oh what a treat! 🎉


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

@QuantumExplorer QuantumExplorer merged commit 023ff85 into v1.4-dev Oct 1, 2024
49 of 84 checks passed
@QuantumExplorer QuantumExplorer deleted the release_1.4.0-dev.3 branch October 1, 2024 00:26
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.

1 participant