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

build(deps): bump github.com/forbole/juno/v3 from 3.1.0 to 3.4.0 #46

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Sep 2, 2022

Bumps github.com/forbole/juno/v3 from 3.1.0 to 3.4.0.

Release notes

Sourced from github.com/forbole/juno/v3's releases.

v3.4.0

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos v0.43.0 or later. If you want to integrate with a chain running Cosmos Stargate, please use v3.4.0-stargate instead.

Changes

  • (#71) Retry RPC client connection upon failure instead of panic
  • (#72) Updated missing blocks parsing
  • (#73) Re-enqueue failed block after average block time

v3.4.0-stargate

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos Stargate. If you want to integrate with a chain running Cosmos v0.43.0 or later, please use v3.4.0 instead.

Changes

  • (#71) Retry RPC client connection upon failure instead of panic
  • (#72) Updated missing blocks parsing
  • (#73) Re-enqueue failed block after average block time

v3.3.0

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos v0.43.0 or later. If you want to integrate with a chain running Cosmos Stargate, please use v3.3.0-stargate instead.

Changes

  • (#67) Added support for concurrent transaction handling
  • (#69) Added ChainID method to the Node type

v3.3.0-stargate

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos Stargate. If you want to integrate with a chain running Cosmos v0.43.0 or later, please use v3.3.0 instead.

Changes

  • (#67) Added support for concurrent transaction handling
  • (#69) Added ChainID method to the Node type

v3.2.1

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos v0.43.0 or later. If you want to integrate with a chain running Cosmos Stargate, please use v3.2.1-stargate instead.

Changes

  • (#68) Added chain_id label to prometheus to improve alert monitoring

v3.2.1-stargate

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos Stargate. If you want to integrate with a chain running Cosmos v0.43.0 or later, please use v3.2.1 instead.

Changes

  • (#68) Added chain_id label to prometheus to improve alert monitoring

v3.2.0

Cosmos compatibility

... (truncated)

Changelog

Sourced from github.com/forbole/juno/v3's changelog.

v3.4.0

Changes

  • (#71) Retry RPC client connection upon failure instead of panic
  • (#72) Updated missing blocks parsing
  • (#73) Re-enqueue failed block after average block time

v3.3.0

Changes

  • (#67) Added support for concurrent transaction handling
  • (#69) Added ChainID method to the Node type

v3.2.1

Changes

  • (#68) Added chain_id label to prometheus to improve alert monitoring

v3.2.0

Changes

  • (#61) Updated v3 migration code to handle database users names with a hyphen
  • (#59) Added parse transactios command to re-fetch missing or incomplete transactions

v3.1.1

Changes

  • Updated IBC to v3.0.0
Commits
  • 8ffed76 chore: release v3.4.0
  • a59db1d fix: re-enqueue failed block after average block time (#73)
  • d752cdb feat: improve block parsing starting height calculations (#72)
  • 65e739b feat: retry upon RPC connection failure (#71)
  • 83b01f5 chore: release v3.3.0
  • 576bf69 chore: release v3.2.2
  • 88a8bc2 feat: add ChainID() method for getting the chain ID from node status (#69)
  • d0d22cf feat: support concurrent transaction handling (#67)
  • 79bc60f chore: release v3.2.1
  • 5c9b026 feat: add chain_id label to prometheus to improve alert monitoring (#68)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/forbole/juno/v3](https://github.com/forbole/juno) from 3.1.0 to 3.4.0.
- [Release notes](https://github.com/forbole/juno/releases)
- [Changelog](https://github.com/forbole/juno/blob/cosmos/v0.44.x/CHANGELOG.md)
- [Commits](forbole/juno@v3.1.0...v3.4.0)

---
updated-dependencies:
- dependency-name: github.com/forbole/juno/v3
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 2, 2022
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Sep 2, 2022

Dependabot tried to add @riccardom as a reviewer to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/onomyprotocol/bdjuno/pulls/46/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the onomyprotocol/bdjuno repository. // See: https://docs.github.com/rest/reference/pulls#request-reviewers-for-a-pull-request

@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Sep 2, 2022

The following labels could not be found: automerge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants