chore(deps): bump cosmossdk.io/x/feegrant from 0.1.1 to 0.2.0#4553
chore(deps): bump cosmossdk.io/x/feegrant from 0.1.1 to 0.2.0#4553dependabot[bot] wants to merge 1 commit into
Conversation
81e26a8 to
0018d85
Compare
93914d4 to
56ee5eb
Compare
56ee5eb to
41d44c4
Compare
|
@dependabot recreate |
Bumps [cosmossdk.io/x/feegrant](https://github.com/cosmos/cosmos-sdk) from 0.1.1 to 0.2.0. - [Release notes](https://github.com/cosmos/cosmos-sdk/releases) - [Changelog](https://github.com/cosmos/cosmos-sdk/blob/v0.2.0/CHANGELOG.md) - [Commits](cosmos/cosmos-sdk@x/nft/v0.1.1...v0.2.0) --- updated-dependencies: - dependency-name: cosmossdk.io/x/feegrant dependency-version: 0.2.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
41d44c4 to
bf72eaa
Compare
| github.com/celestiaorg/rsmt2d v0.15.1 | ||
| github.com/cometbft/cometbft v0.38.17 | ||
| github.com/cosmos/cosmos-sdk v0.50.13 | ||
| github.com/cosmos/cosmos-sdk v0.53.0 |
There was a problem hiding this comment.
🔴 cosmos-sdk require bumped to v0.53.0 but replace directive still pins to celestiaorg fork v0.51.6, creating dependency mismatch
The PR bumps github.com/cosmos/cosmos-sdk from v0.50.13 to v0.53.0 in the require block (as a transitive requirement of feegrant v0.2.0), but the replace directive at go.mod:204 still maps it to github.com/celestiaorg/cosmos-sdk v0.51.6. This means the actual SDK used at build time is v0.51.6, while the new indirect dependencies (cosmossdk.io/collections v1.2.0, cosmossdk.io/x/tx v0.14.0, cosmossdk.io/schema v1.1.0) and feegrant v0.2.0 itself are designed for cosmos-sdk v0.53.0. These are not replaced and will be fetched as-is — collections jumped from v0.4.0 to v1.2.0 (a major version change), and x/tx from v0.13.8 to v0.14.0. These newer module versions likely reference types or interfaces from cosmos-sdk v0.53.0 that don't exist in the v0.51.6 fork, leading to compilation failures or runtime incompatibilities. This appears to be an automated dependency bump that did not account for the project's replace directives.
Prompt for agents
The cosmos-sdk require version in go.mod line 22 was bumped from v0.50.13 to v0.53.0 to satisfy feegrant v0.2.0's transitive dependency, but the replace directive at go.mod line 204 (github.com/cosmos/cosmos-sdk => github.com/celestiaorg/cosmos-sdk v0.51.6) was not updated. Either:
1. Revert the feegrant bump back to v0.1.1 and revert all the associated transitive dependency bumps (cosmos-sdk back to v0.50.13, collections back to v0.4.0, x/tx back to v0.13.8, remove schema v1.1.0), OR
2. Update the celestiaorg/cosmos-sdk fork to a version compatible with v0.53.0 and update the replace directive accordingly, then verify all transitive dependencies are compatible.
Option 1 is safer if the fork hasn't been updated. Affected lines: go.mod line 22 (cosmos-sdk require), go.mod line 9 (feegrant require), go.mod line 94 (collections indirect), go.mod line 98 (schema indirect), go.mod line 101 (x/tx indirect), and go.mod line 204 (replace directive).
Was this helpful? React with 👍 or 👎 to provide feedback.
|
This bump is incompatible with the project's cosmos-sdk fork.
As a result, This bump cannot be applied until the cosmos-sdk fork is updated to include the |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps cosmossdk.io/x/feegrant from 0.1.1 to 0.2.0.
Release notes
Sourced from cosmossdk.io/x/feegrant's releases.
Changelog
Sourced from cosmossdk.io/x/feegrant's changelog.
Commits
8e4d6a5Merge branch 'master' into develop72bebc6Merge pull request #819 from cosmos/release/v0.14.04807a19Merge pull request #774 from fedekunze/fedekunze/README40b193fupdate changelog1074ab6version and changelog9722f41deps, changelog, version56c3ae4Merge branch 'develop' into fedekunze/READMEc155a82addressed Rige's comments9b246ecUpdate README.md52f317aMerge pull request #800 from cosmos/rigel/tick-endblockYou can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)