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

feat: explicit config file entry for ABCI client type #20080

Closed
wants to merge 787 commits into from

Conversation

JimLarson
Copy link
Contributor

@JimLarson JimLarson commented Apr 18, 2024

Description

Refs: Agoric/agoric-sdk#9224

Add an explicit entry for abci-client-type in the TOML file. The setting can be done in the file but is overridden by when the command-line flag is set.

Note that this entry is unlike the other entries in the "base config" part of the TOML file, in that there are no BaseApp.Get/SetABCIClientType() methods, option helpers, etc. This makes it more like the various start command flags that do not have explicit config fields, e.g. --with-tendermint or --trace-store. This seems appropriate for a setting that is used near the "top" of the start command.

Note that even without this change, the option can be set in the config/app.toml file. This just makes the entry part of the automatically-generated TOML file.

Note that the default value is now specified both in the flag definition and in the default config constructor, as some of the other flags are. It's confusing to think about which one takes precedence, so they should just be kept in sync.

Tested the following:

  • start with default toml file which includes and explicit entry to the default "committing" value
  • start with an illegal value - fails as expected
  • start with non-default valid value "local"
  • start with line removed from app.toml
  • override with flag set to an illegal value - fails as expected
  • override with flag set to "committing"
  • restore app.toml entry and override with a different legal value
  • override with illegal flag - still fails as expected.

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • New Features
    • Introduced a structured changelog for the Agoric fork of the Cosmos SDK.
    • Added a guide on branch management for the Agoric project.
    • Implemented changelog generation in the release process.
  • Documentation
    • Updated Go version requirements in README.md.
    • Added upgrade instructions for Cosmos SDK v0.46.x in UPGRADING.md.
    • Introduced new release notes and process documentation.
  • Bug Fixes
    • Reverted to a stable version of actions/labeler to resolve issues.
  • Refactor
    • Updated Go version across various workflows and Dockerfile.
    • Adjusted automated merging and backporting rules in .mergify.yml.
  • Chores
    • Updated .gitignore to exclude new directories and files.
    • Updated repository URLs and dependencies in the Makefile.
  • Style
    • Removed and added specific linters to improve code quality checks.

julienrbrt and others added 30 commits October 19, 2022 12:33
Co-authored-by: likhita-809 <78951027+likhita-809@users.noreply.github.com>
Co-authored-by: Sai Kumar <17549398+gsk967@users.noreply.github.com>
Co-authored-by: Aleksandr Bezobchuk <alexanderbez@users.noreply.github.com>
Co-authored-by: Facundo Medica <14063057+facundomedica@users.noreply.github.com>
Co-authored-by: emidev98 <49301655+emidev98@users.noreply.github.com>
Co-authored-by: colin axnér <25233464+colin-axner@users.noreply.github.com>
Co-authored-by: Marko Baricevic <markobaricevic3778@gmail.com>

Co-authored-by: likhita-809 <78951027+likhita-809@users.noreply.github.com>
Co-authored-by: Sai Kumar <17549398+gsk967@users.noreply.github.com>
Co-authored-by: Aleksandr Bezobchuk <alexanderbez@users.noreply.github.com>
Co-authored-by: Facundo Medica <14063057+facundomedica@users.noreply.github.com>
Co-authored-by: emidev98 <49301655+emidev98@users.noreply.github.com>
Co-authored-by: colin axnér <25233464+colin-axner@users.noreply.github.com>
Co-authored-by: Marko Baricevic <markobaricevic3778@gmail.com>
* chore: bump tendermint to `0.34.22`

* update changelog

* update changelog

* go mod tidy all
…tConfig. (cosmos#13610)

* Populate the PruningKeepEvery config entry in GetConfig.

* Update changlog.
* docs: add ApplicationQueryService release notes

* updates

Co-authored-by: Julien Robert <julien@rbrt.fr>
…os#13612) (cosmos#13616)

* feat(cli): add module-account cli cmd and grpc get api (cosmos#13612)

(cherry picked from commit ddf5cf0)

# Conflicts:
#	CHANGELOG.md
#	api/cosmos/auth/v1beta1/query.pulsar.go
#	api/cosmos/auth/v1beta1/query_grpc.pb.go
#	x/auth/client/testutil/suite.go
#	x/auth/types/query.pb.go

* fix conflicts

* updates

* updates

Co-authored-by: Sai Kumar <17549398+gsk967@users.noreply.github.com>
Co-authored-by: Julien Robert <julien@rbrt.fr>
…#12474) (cosmos#13598)

* fix(x/auth): allow multiple = signs in `GetTxsEvent` (cosmos#12474)

(cherry picked from commit 18da0e9)

# Conflicts:
#	CHANGELOG.md

* fix changelog

* changelog

* fix: flakey test

Co-authored-by: Tyler <48813565+technicallyty@users.noreply.github.com>
Co-authored-by: Julien Robert <julien@rbrt.fr>
…os#13612) (cosmos#13617)

* feat(cli): add module-account cli cmd and grpc get api (cosmos#13612)

(cherry picked from commit ddf5cf0)

# Conflicts:
#	CHANGELOG.md
#	api/cosmos/auth/v1beta1/query.pulsar.go
#	api/cosmos/auth/v1beta1/query_grpc.pb.go
#	proto/cosmos/auth/v1beta1/query.proto
#	tests/e2e/auth/suite.go
#	x/auth/client/cli/query.go
#	x/auth/keeper/grpc_query.go
#	x/auth/keeper/grpc_query_test.go
#	x/auth/types/query.pb.go
#	x/auth/types/query.pb.gw.go

* update changelog

* fix conflicts

Co-authored-by: Sai Kumar <17549398+gsk967@users.noreply.github.com>
Co-authored-by: Julien Robert <julien@rbrt.fr>
* chore: prepare 0.45.10 changelog

* default release notes

* period
…cosmos#13656) (cosmos#13659)

(cherry picked from commit c833190)

Co-authored-by: William Chong <6198816+williamchong@users.noreply.github.com>
…smos#13656) (cosmos#13660)

* feat(cli): Add iavl-disable-fastnode cmd flag with proper description (cosmos#13656)

(cherry picked from commit c833190)

# Conflicts:
#	server/start.go

* fix conflicts

Co-authored-by: William Chong <6198816+williamchong@users.noreply.github.com>
Co-authored-by: Julien Robert <julien@rbrt.fr>
* chore: prepare 0.46.4 changelog

* wording

* updates

* updates
* ci: notify for 0.45.x releases

* update changelog
* feat: notify for 0.46.x releases

* updates changelog
* ci: modifying docs in 0.46 should not redeploy docs

* updates
…osmos#13804)

* refactor: add error log when iavl set failed (cosmos#13803)

* add error log when iavl set failed

Ref: cosmos#12012

* Update CHANGELOG.md

* play safe

(cherry picked from commit 22f3261)

# Conflicts:
#	CHANGELOG.md

* fix conflicts

Co-authored-by: yihuang <huang@crypto.com>
* chore: prepare 0.45.11 release

* no features in 0.45.11

* Update RELEASE_NOTES.md

Co-authored-by: Aleksandr Bezobchuk <alexanderbez@users.noreply.github.com>

* update release notes

Co-authored-by: Aleksandr Bezobchuk <alexanderbez@users.noreply.github.com>
Setting the flag still works and takes precedence.
Copy link
Contributor

coderabbitai bot commented Apr 18, 2024

Walkthrough

Walkthrough

This update primarily focuses on upgrading the Go language version from 1.18 to 1.19 across various GitHub workflows and Docker configurations. It also involves updates to linter settings, modifications in automation rules for merging and releasing, and enhancements in documentation and configuration files to align with the new version. Notably, there's a shift in linter tools and an introduction of structured changelogs and branch management guides for the Agoric project.

Changes

Files Change Summary
.github/workflows/... Updated Go version to 1.19 in multiple workflow files. Added tag triggers and updated actions in lint.yml. Introduced Slack notifications in release.yml. Reverted to actions/labeler v4 in labeler.yml.
.gitignore Added tools/ directory and debug_container.dot, updated paths for Latex and Graphviz.
.golangci.yml Removed several linters, added gofumpt, and updated exclusion rules.
.goreleaser.yml Modified changelog configuration to include generation.
.mergify.yml Adjusted automerging and backporting rules.
Agoric-branch-notes.md, CHANGELOG-Agoric.md Introduced branch management guide and structured changelog for Agoric fork.
Dockerfile Updated base image to golang:1.19-alpine.
Makefile Updated build commands, repository URLs, and added gofumpt.
README.md, RELEASE_NOTES.md, RELEASE_PROCESS.md, SECURITY.md, UPGRADING.md Updated Go version requirements, URLs, and provided detailed upgrading instructions.

Recent Review Details

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 5e7aae0 and e4befa6.
Files ignored due to path filters (48)
  • api/cosmos/app/v1alpha1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/auth/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/authz/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/authz/v1beta1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/bank/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/bank/v1beta1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/base/reflection/v1beta1/reflection_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/base/reflection/v2alpha1/reflection_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/base/tendermint/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/crisis/v1beta1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/distribution/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/distribution/v1beta1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/evidence/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/evidence/v1beta1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/feegrant/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/feegrant/v1beta1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/gov/v1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/gov/v1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/gov/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/gov/v1beta1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/group/v1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/group/v1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/mint/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/nft/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/nft/v1beta1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/params/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/slashing/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/slashing/v1beta1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/staking/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/staking/v1beta1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/tx/v1beta1/service_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/upgrade/v1beta1/query_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/upgrade/v1beta1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/cosmos/vesting/v1beta1/tx_grpc.pb.go is excluded by !**/*.pb.go
  • api/go.mod is excluded by !**/*.mod
  • api/go.sum is excluded by !**/*.sum
  • api/tendermint/abci/types_grpc.pb.go is excluded by !**/*.pb.go
  • client/grpc/node/query.pb.go is excluded by !**/*.pb.go
  • client/grpc/node/query.pb.gw.go is excluded by !**/*.pb.gw.go
  • client/grpc/tmservice/query.pb.go is excluded by !**/*.pb.go
  • client/grpc/tmservice/types.pb.go is excluded by !**/*.pb.go
  • client/v2/go.mod is excluded by !**/*.mod
  • client/v2/internal/buf.lock is excluded by !**/*.lock
  • contrib/rosetta/rosetta-ci/data.tar.gz is excluded by !**/*.gz
  • core/go.mod is excluded by !**/*.mod
  • core/go.sum is excluded by !**/*.sum
  • cosmovisor/go.mod is excluded by !**/*.mod
  • cosmovisor/go.sum is excluded by !**/*.sum
Files selected for processing (21)
  • .github/workflows/codeql-analysis.yml (1 hunks)
  • .github/workflows/cosmovisor-release.yml (1 hunks)
  • .github/workflows/labeler.yml (1 hunks)
  • .github/workflows/lint.yml (1 hunks)
  • .github/workflows/release.yml (2 hunks)
  • .github/workflows/sims.yml.DISABLED (5 hunks)
  • .github/workflows/test-race.yml (4 hunks)
  • .github/workflows/test.yml (7 hunks)
  • .gitignore (2 hunks)
  • .golangci.yml (3 hunks)
  • .goreleaser.yml (1 hunks)
  • .mergify.yml (1 hunks)
  • Agoric-branch-notes.md (1 hunks)
  • CHANGELOG-Agoric.md (1 hunks)
  • Dockerfile (1 hunks)
  • Makefile (6 hunks)
  • README.md (2 hunks)
  • RELEASE_NOTES.md (1 hunks)
  • RELEASE_PROCESS.md (2 hunks)
  • SECURITY.md (1 hunks)
  • UPGRADING.md (1 hunks)
Files skipped from review due to trivial changes (1)
  • .github/workflows/labeler.yml
Additional Context Used
LanguageTool (245)
Agoric-branch-notes.md (24)

Near line 3: Possible spelling mistake found.
Context: ...anches: - Agoric - the trunk for our cosmos-sdk fork, used by [agoric-sdk](https://gith...


Near line 3: Possible spelling mistake found.
Context: ...trunk for our cosmos-sdk fork, used by agoric-sdk....


Near line 6: Although a hyphen is possible, it is not necessary in a compound modifier in which the first word is an adverb that ends in ‘ly’.
Context: ... - Agoric-vX.Y.Z-alpha.agoric.A.x - a lazily-created release branch. - Branched off of r...


Near line 7: ‘off of’ might be wordy. Consider a shorter alternative.
Context: ...-created release branch. - Branched off of release tag vX.Y.Z-alpha.agoric.A. ...


Near line 7: Add a space between sentences.
Context: ...anch. - Branched off of release tag vX.Y.Z-alpha.agoric.A. - Created when w...


Near line 9: You might be missing the article “the” here.
Context: ...refer to contain only cherry-picks from trunk. - Pattern can be extended to sub-sub-b...


Near line 14: This sentence does not start with an uppercase letter.
Context: ... convention: - vX.Y.Z-alpha.agoric.A for tagged releases on the Agoric branch:...


Near line 14: Possible spelling mistake found.
Context: ...ha.agoric.Afor tagged releases on theAgoricbranch: -vX.Y.Z` is the version ...


Near line 15: Possible spelling mistake found.
Context: ...version of the latest integrated cosmos/cosmos-sdk release. - The A is an increasing...


Near line 16: Possible spelling mistake found.
Context: ...after the integration of a new cosmos/cosmos-sdk release. -vX.Y.Z-alpha.agoric.A.B` fo...


Near line 17: This sentence does not start with an uppercase letter.
Context: ...dk release. - vX.Y.Z-alpha.agoric.A.B for "patch" releases on branch `Agoric-vX.Y...


Near line 17: Add a space between sentences.
Context: ...ric.A.Bfor "patch" releases on branchAgoric-vX.Y.Z-alpha.agoric.A.x. - B` starts a...


Near line 18: This sentence does not start with an uppercase letter.
Context: ...ric-vX.Y.Z-alpha.agoric.A.x. - B` starts at 1 and increases sequentially. - Patt...


Near line 19: A determiner appears to be missing. Consider inserting it.
Context: ...arts at 1 and increases sequentially. - Pattern can be extended to releases on sub-sub-...


Near line 23: Possible spelling mistake found.
Context: ...es: - New features should be landed on Agoric first, then cherry-picked to a release...


Near line 24: ‘off of’ might be wordy. Consider a shorter alternative.
Context: ...eded. - Create a new development branch off of Agoric. - Test, review, merge PR with...


Near line 24: Possible spelling mistake found.
Context: ... Create a new development branch off of Agoric. - Test, review, merge PR with `autome...


Near line 25: Possible spelling mistake found.
Context: ...Agoric. - Test, review, merge PR with automerge label for mergify.io - Don't forge...


Near line 28: Possible spelling mistake found.
Context: ... change and a link to its PR. Upon new cosmos-sdk releases, see [upgrading the Interchain...


Near line 31: Unpaired symbol: ‘[’ seems to be missing
Context: ...erchain-Stack). Historical work: - ag0 [Agoric ...


Near line 31: Possible spelling mistake found.
Context: ...- ag0 Agoric mainnet phase 0'...


Near line 31: Possible spelling mistake found.
Context: ...(https://github.com/Agoric/ag0) Agoric mainnet phase 0's [gaiad...


Near line 32: Possible spelling mistake found.
Context: ...innet](https://agoric.com) phase 0's gaiad-equivalent - `Ago...


Near line 34: Possible spelling mistake found.
Context: ...ag0` - should be identical to cosmos/cosmos-sdk ...

CHANGELOG-Agoric.md (39)

Near line 36: Possible spelling mistake found.
Context: ...angelog.com/en/1.0.0/ --> # Changelog (Agoric fork) ## Unreleased ### Improvements ...


Near line 42: Possible spelling mistake found.
Context: ...gurable fee collector module account in DeductFeeDecorator. * (server) [#409](https://github.com/a...


Near line 43: Possible spelling mistake found.
Context: ...abs/cosmos-sdk/pull/409) Flag to select ABCI client type. * (deps) [#412](https://gi...


Near line 44: Possible spelling mistake found.
Context: ...m/agoric-labs/pull/412) Bump iavl to v0.19.7 * (baseapp) [#415](https://g...


Near line 45: Possible spelling mistake found.
Context: ...s-sdk/pull/412) Bump iavl to v0.19.7 * (baseapp) [#415](https://github.com/agoric-labs/...


Near line 49: Possible spelling mistake found.
Context: ...n for event history. ### Bug Fixes * (baseapp) [#413](https://github.com/agoric-labs/...


Near line 50: Possible spelling mistake found.
Context: ...e events from simulated transactions * (baseapp) [#415](https://github.com/agoric-labs/...


Near line 54: Possible spelling mistake found.
Context: ...tory. ### API Breaking * (auth, bank) Agoric/agoric-sdk#8989 Remove deprecated lien ...


Near line 54: Possible spelling mistake found.
Context: ...### API Breaking * (auth, bank) Agoric/agoric-sdk#8989 Remove deprecated lien support ##...


Near line 54: Please check whether ‘lean’ (thin) might be the correct word here instead of ‘lien’ (a form of security interest).
Context: ...goric/agoric-sdk#8989 Remove deprecated lien support ## v0.46.16-alpha.agoric.2 -...


Near line 58: Possible spelling mistake found.
Context: ...0.46.16-alpha.agoric.2- 2024-02-08 * Agoric/agoric-sdk#8871 Havetx gov submit-pro...


Near line 58: Possible spelling mistake found.
Context: ...-alpha.agoric.2- 2024-02-08 * Agoric/agoric-sdk#8871 Havetx gov submit-proposal` acce...


Near line 58: Possible spelling mistake found.
Context: ...24-02-08 * Agoric/agoric-sdk#8871 Have tx gov submit-proposal accept either new ...


Near line 62: Possible spelling mistake found.
Context: ...com//pull/19371) Avoid cli redundant log in stdout, log to stderr ...


Near line 66: Possible spelling mistake found.
Context: ...0.46.16-alpha.agoric.1` - 2024-02-05 * Agoric/agoric-sdk#8224 Merge [cosmos/cosmos-sd...


Near line 66: Possible spelling mistake found.
Context: ...-alpha.agoric.1` - 2024-02-05 * Agoric/agoric-sdk#8224 Merge [cosmos/cosmos-sdk v0.46.16]...


Near line 66: Unpaired symbol: ‘]’ seems to be missing
Context: ...4-02-05 * Agoric/agoric-sdk#8224 Merge [cosmos/cosmos-sdk v0.46.16](https://gith...


Near line 66: Possible spelling mistake found.
Context: ... * Agoric/agoric-sdk#8224 Merge [cosmos/cosmos-sdk v0.46.16](https://github.com/cosmos/cos...


Near line 70: Possible spelling mistake found.
Context: ...eleases/tag/v0.46.16) ### Bug Fixes * Agoric/agoric-sdk#8719 MsgClawback returns the...


Near line 70: Possible spelling mistake found.
Context: .../tag/v0.46.16) ### Bug Fixes * Agoric/agoric-sdk#8719 MsgClawback returns the wrong Type...


Near line 70: Possible spelling mistake found.
Context: ...### Bug Fixes * Agoric/agoric-sdk#8719 MsgClawback returns the wrong Type ## `v0.45.16-al...


Near line 80: Possible spelling mistake found.
Context: ...oric.2` - 2023-11-08 ### Bug Fixes * (baseapp) [#337](https://github.com/agoric-labs/...


Near line 80: Possible spelling mistake found.
Context: ...vert #305 which causes test failures in agoric-sdk ## v0.45.16-alpha.agoric.1 - 2023-09...


Near line 86: Possible spelling mistake found.
Context: ...ic.1` - 2023-09-22 ### Improvements * Agoric/agoric-sdk#8223 Merge [cosmos/cosmos-sd...


Near line 86: Possible spelling mistake found.
Context: ... 2023-09-22 ### Improvements * Agoric/agoric-sdk#8223 Merge [cosmos/cosmos-sdk v0.45.16]...


Near line 86: Unpaired symbol: ‘]’ seems to be missing
Context: ...vements * Agoric/agoric-sdk#8223 Merge [cosmos/cosmos-sdk v0.45.16](https://gith...


Near line 86: Possible spelling mistake found.
Context: ... * Agoric/agoric-sdk#8223 Merge [cosmos/cosmos-sdk v0.45.16](https://github.com/cosmos/cos...


Near line 87: Possible spelling mistake found.
Context: ...goric-labs/cosmos-sdk/pull/303) Improve vestcalc comments and documentation. ### Bug Fi...


Near line 91: Unpaired symbol: ‘]’ seems to be missing
Context: ...aise the per snapshot item limit. Fixes [Agoric/agoric-sdk#8325](https://github.c...


Near line 91: Possible spelling mistake found.
Context: ...ise the per snapshot item limit. Fixes [Agoric/agoric-sdk#8325](https://github.com/Ago...


Near line 91: Possible spelling mistake found.
Context: ... per snapshot item limit. Fixes [Agoric/agoric-sdk#8325](https://github.com/Agoric/agoric-...


Near line 92: Possible spelling mistake found.
Context: ...b.com/Agoric/agoric-sdk/issues/8325) * (baseapp) [#305](https://github.com/agoric-labs/...


Near line 92: Unpaired symbol: ‘]’ seems to be missing
Context: ... blocks beyond the halt height. Port of [#16639](https://github....


Near line 92: Possible spelling mistake found.
Context: ...beyond the halt height. Port of [#16639](https://github.com/cosmos/cosmos...


Near line 98: Possible spelling mistake found.
Context: ...l/13400) Fix snapshot checksum issue in golang 1.19. ### API Breaking Changes * (sto...


Near line 102: Possible missing preposition found.
Context: ...ithub.com//pull/11825) Make extension snapshotter interface safer t...


Near line 102: Possible spelling mistake found.
Context: ...s/cosmos-sdk/pull/11825) Make extension snapshotter interface safer to use, renamed the uti...


Near line 102: Possible spelling mistake found.
Context: ...safer to use, renamed the util function WriteExtensionItem to WriteExtensionPayload.


Near line 102: Possible spelling mistake found.
Context: ...e util function WriteExtensionItem to WriteExtensionPayload.

README.md (12)

Near line 40: Possible spelling mistake found.
Context: ... for building blockchain applications. [Tendermint Core (BFT Consensus)](https://github.co...


Near line 65: Possible spelling mistake found.
Context: ...ls): notable frameworks and modules. + CosmJS: the...


Near line 65: Unpaired symbol: ‘[’ seems to be missing
Context: ...otable frameworks and modules. + CosmJS: the ...


Near line 65: This expression is usually spelled with a hyphen.
Context: .../cosmjs): the Swiss Army knife to power JavaScript based client solutions. ### Cosmos Hub Mainn...


Near line 69: Possible spelling mistake found.
Context: ...ub Mainnet The Cosmos Hub application, gaia, has moved to its own [cosmos/gaia rep...


Near line 69: Possible spelling mistake found.
Context: ...n, gaia, has moved to its own [cosmos/gaia repository](https://github.com/cosmos/g...


Near line 69: Possible spelling mistake found.
Context: .../gaia). Go there to join the Cosmos Hub mainnet and more. ### Inter-Blockchain Communi...


Near line 73: Possible spelling mistake found.
Context: ...Cosmos SDK has moved to its own [cosmos/ibc-go repository](https://github.com/cosmos/i...


Near line 77: Consider using a different verb to strengthen your wording.
Context: ...b.com/ignite-hq/cli) to get started and speed up development. ## Disambiguation This C...


Near line 81: Possible spelling mistake found.
Context: ...mos) project (yet). Many thanks to Evan Coury and Ovidiu (@skidding) for this Github ...


Near line 81: Possible spelling mistake found.
Context: ...ct (yet). Many thanks to Evan Coury and Ovidiu (@skidding) for this Github organizatio...


Near line 81: The official name of this software platform is spelled with a capital “H”.
Context: ...n Coury and Ovidiu (@skidding) for this Github organization name. As per our agreement...

RELEASE_NOTES.md (2)

Near line 20: This sentence does not start with an uppercase letter.
Context: ...6.16 ## End-of-Life Notice v0.46.16 is the last release of the v0.46.x line....


Near line 21: Possible spelling mistake found.
Context: ...ures, improvements or bug fixes will be backported to the v0.46.x line. Per our policy, ...

RELEASE_PROCESS.md (52)

Near line 7: Possible spelling mistake found.
Context: ...e_ is an increment of the first number (eg: v1.2v2.0.0) or the _point numbe...


Near line 7: Possible spelling mistake found.
Context: ...1.2v2.0.0) or the _point number_ (eg: v1.1 → v1.2.0`, also called _point re...


Near line 21: Possible spelling mistake found.
Context: ... that the main works fine we create a release/vY branch (going forward known a release ...


Near line 21: Possible spelling mistake found.
Context: ...with the patch part substituted to x (eg: 0.42.x, 1.0.x). Ensure the release bra...


Near line 23: Possible spelling mistake found.
Context: ...stances arise** * update the GitHub mergify integration by adding instructions for ...


Near line 23: Possible spelling mistake found.
Context: ...y adding instructions for automatically backporting commits from main to the release/vY...


Near line 23: Possible spelling mistake found.
Context: ... backporting commits from main to the release/vY using the backport/Y label. * In the...


Near line 23: Possible spelling mistake found.
Context: ...om main to the release/vY using the backport/Y label. * In the release branch, prep...


Near line 24: Possible typo. Did you mean “the” or “All”?
Context: ...ranch, prepare a new version section in the CHANGELOG.md * All links must be link-ified: `$ python ./s...


Near line 25: Possible spelling mistake found.
Context: ... CHANGELOG.md * All links must be link-ified: `$ python ./scripts/linkify_changelog....


Near line 26: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...a RELEASE_CHANGELOG.md, this is needed so the bot knows which entries to add to t...


Near line 27: Possible typo: you repeated a whitespace
Context: ...nnotated git tag for a release candidate (eg: git tag -a v1.1.0-rc1) in the rel...


Near line 27: Possible spelling mistake found.
Context: ...tated git tag for a release candidate (eg: git tag -a v1.1.0-rc1) in the releas...


Near line 28: This sentence does not start with an uppercase letter.
Context: ....1.0-rc1`) in the release branch. * from this point we unfreeze main. * the ...


Near line 28: It appears that a comma is missing.
Context: ... in the release branch. * from this point we unfreeze main. * the SDK teams c...


Near line 29: This sentence does not start with an uppercase letter.
Context: ...from this point we unfreeze main. * the SDK teams collaborate and do their best...


Near line 29: Possible spelling mistake found.
Context: ...ms collaborate and do their best to run testnets in order to validate the release. *...


Near line 29: Consider a shorter alternative to avoid wordiness.
Context: ...orate and do their best to run testnets in order to validate the release. * when bugs a...


Near line 30: This sentence does not start with an uppercase letter.
Context: ...in order to validate the release. * when bugs are found, create a PR for main,...


Near line 30: Possible spelling mistake found.
Context: ... are found, create a PR for main, and backport fixes to the release branch. * crea...


Near line 31: This sentence does not start with an uppercase letter.
Context: ...port fixes to the release branch. * create new release candidate tags after bugs a...


Near line 34: This sentence does not start with an uppercase letter.
Context: ...ase: * update CHANGELOG.md. * run gofumpt -w -l . to format the code. ...


Near line 34: Don’t put a space before the full stop.
Context: ... * update CHANGELOG.md. * run gofumpt -w -l . to format the code. * create a new...


Near line 35: This sentence does not start with an uppercase letter.
Context: ...umpt -w -l .to format the code. * create a new annotated git tag (eggit -a v1....


Near line 35: Possible spelling mistake found.
Context: .... * create a new annotated git tag (eg git -a v1.1.0) in the release branch....


Near line 38: Possible spelling mistake found.
Context: ... * Create a GitHub release. Following semver philosophy, point releases after `v1.0...


Near line 47: Possible spelling mistake found.
Context: ...e_ is an increment of the patch number (eg: v1.2.0v1.2.1). **Patch release...


Near line 51: Possible spelling mistake found.
Context: ...lease branch should come from main by backporting PRs (usually done by automatic cherry p...


Near line 51: This word is normally spelled with a hyphen.
Context: ...kporting PRs (usually done by automatic cherry pick followed by a PRs to the release branch...


Near line 51: The plural noun “PRs” cannot be used with the article “a”. Did you mean “a PR” or “PRs”?
Context: ...ne by automatic cherry pick followed by a PRs to the release branch). The backports m...


Near line 51: Possible spelling mistake found.
Context: ...ed by a PRs to the release branch). The backports must be marked using backport/Y label...


Near line 51: Possible spelling mistake found.
Context: ...ch). The backports must be marked using backport/Y label in PR for main. It is the PR a...


Near line 61: This sentence does not start with an uppercase letter.
Context: ...required for the next patch release: * update CHANGELOG.md. * create a new annotate...


Near line 62: This sentence does not start with an uppercase letter.
Context: ...ch release: * update CHANGELOG.md. * create a new annotated git tag (eg `git -a v1....


Near line 62: Possible spelling mistake found.
Context: ....md. * create a new annotated git tag (eg git -a v1.1.0`) in the release branch....


Near line 67: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ease) until they reach End Of Life. Major Release series is maintained in complia...


Near line 73: Possible spelling mistake found.
Context: ...ted until 2022-02-09. A fairly strict bugfix-only rule applies to pull requests that ar...


Near line 74: Possible spelling mistake found.
Context: ...ted until 2022-07-17. A fairly strict bugfix-only rule applies to pull requests that ar...


Near line 100: Did you mean ‘different from’? ‘Different than’ is often considered colloquial style.
Context: ...ements for stable changes are different than those that are candidates to be merged ...


Near line 101: This phrase might be unnecessarily wordy.
Context: .... When preparing future major releases, our aim is to design the most elegant, user-friend...


Near line 111: Possible spelling mistake found.
Context: ...tween SDK versions, under the migrate subcommand. Only migration scripts between stable ...


Near line 115: Possible typo: you repeated a word
Context: ...e Release Update (SRU) * High-impact bugs * Bugs that may directly cause a security vuln...


Near line 130: Possible spelling mistake found.
Context: ... machine changes. * Breaking changes in Protobuf definitions, as specified in [ADR-044](...


Near line 131: The plural noun “Changes” expects the verb form “introduce”.
Context: ...-updates-guidelines.md). * Changes that introduces API breakages (e.g. public functions an...


Near line 143: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...se state corruption or data loss. * Bugs that may directly or indirectly cause a...


Near line 152: Possible spelling mistake found.
Context: ...ases: * State machine changes. * Protobug-breaking changes, as specified in [ADR-044](ht...


Near line 152: Possible typo: you repeated a whitespace
Context: ...s/architecture/adr-044-protobuf-updates- guidelines.md). * **Client-breaking chan...


Near line 164: Possible spelling mistake found.
Context: ... the bug on users and justification for backporting the fix to the stable release. * A *...


Near line 190: Possible spelling mistake found.
Context: ...luate and approve or reject updates and backports to Cosmos-SDK Stable Release series, ac...


Near line 194: Possible spelling mistake found.
Context: ...Decisions are made by consensus. Their responsibilites include: * Driving the Stable Release ...


Near line 200: A comma may be missing after the conjunctive/linking adverb ‘Currently’.
Context: ...appointed by the Interchain Foundation. Currently residing Stable Release Managers: * @c...


Near line 203: Possible spelling mistake found.
Context: ...son - Cory Levinson * @AmauryM - Amaury Martiny * @robert-zaremba - Robert Zaremba

SECURITY.md (19)

Near line 4: Possible spelling mistake found.
Context: ...ogram](https://hackerone.com/cosmos) on HackerOne. DO NOT open a public issue on the re...


Near line 16: Possible spelling mistake found.
Context: ...ulnerabilities we are interested in for Tendermint and other lower-level libraries (eg. [I...


Near line 16: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...ermint and other lower-level libraries (eg. IAVL)...


Near line 16: Possible spelling mistake found.
Context: ...t and other lower-level libraries (eg. IAVL). ###...


Near line 41: Possible spelling mistake found.
Context: ...ging into the code. ### How we process Tx parameters * Integer operations on tx ...


Near line 43: Possible spelling mistake found.
Context: ... Tx parameters * Integer operations on tx parameters, especially sdk.Int / `sdk...


Near line 43: Add a space between sentences.
Context: ...operations on tx parameters, especially sdk.Int / sdk.Dec * Gas calculation & parame...


Near line 45: Possible spelling mistake found.
Context: ...* Gas calculation & parameter choices * Tx signature verification (see [`x/auth/an...


Near line 46: This expression is usually spelled with a hyphen.
Context: ...vectors (perhaps due to gas weighting / non constant timing) ### Handling private keys * H...


Near line 52: Possible spelling mistake found.
Context: ... memory-access patterns when decrypting privkey ## Disclosure Process The Cosmos SDK ...


Near line 59: Possible spelling mistake found.
Context: ...e Cosmos SDK team collaborates with the Tendermint and Gaia teams to determine the vulnera...


Near line 63: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short).
Context: ...notification, fixes are applied publicly and new releases are issued. 1. The Gaia te...


Near line 64: Possible spelling mistake found.
Context: ... issued. 1. The Gaia team updates their Tendermint Core and Cosmos SDK dependencies to use...


Near line 64: Possible missing comma found.
Context: ...nd Cosmos SDK dependencies to use these releases and then issues new Gaia releases. 1. A...


Near line 65: Possible spelling mistake found.
Context: ...es. 1. After releases are available for Tendermint Core, Cosmos SDK, and Gaia, we notify t...


Near line 65: The official name of this software platform is spelled with a capital “H”.
Context: ... We also publish a Security Advisory on Github and publish the CVE, as long as the Sec...


Near line 104: Possible spelling mistake found.
Context: ...idators (COMMS LEAD) 1. Test fixes on a testnet (COSMOS SDK ENG) 1. Write “Security Ad...


Near line 104: Possible typo: you repeated a whitespace
Context: ... (COMMS LEAD) 1. Test fixes on a testnet (COSMOS SDK ENG) 1. Write “Security Advi...


Near line 120: Possible typo: you repeated a whitespace
Context: ...sing social channels (Telegram, Discord) that the release is out (COMMS LEAD) 1. ...

UPGRADING.md (97)

Near line 17: Possible typo: you repeated a whitespace
Context: ...d improvements has been done: | Package | Previous | C...


Near line 17: Possible typo: you repeated a whitespace
Context: ...s has been done: | Package | Previous | Current |...


Near line 17: Possible typo: you repeated a whitespace
Context: ...ious | Current | | --------- | ------------------------...


Near line 19: Possible spelling mistake found.
Context: ...----------------------------------- | | simapp | encodingConfig.Marshaler ...


Near line 19: Possible typo: you repeated a whitespace
Context: ...--------------------------- | | simapp | encodingConfig.Marshaler | `...


Near line 19: Add a space between sentences.
Context: ...----------------------- | | simapp | encodingConfig.Marshaler | encodingConfig.Codec ...


Near line 19: Possible typo: you repeated a whitespace
Context: ...| simapp | encodingConfig.Marshaler | encodingConfig.Codec |...


Near line 19: Add a space between sentences.
Context: ... | encodingConfig.Marshaler | encodingConfig.Codec | | simapp | `FundAcc...


Near line 19: Possible typo: you repeated a whitespace
Context: ...shaler |encodingConfig.Codec | |simapp |FundAccount, FundModu...


Near line 20: Possible spelling mistake found.
Context: ...encodingConfig.Codec | |simapp |FundAccount, FundModuleAccount` ...


Near line 20: Possible typo: you repeated a whitespace
Context: ...Config.Codec | |simapp |FundAccount, FundModuleAccount` | F...


Near line 20: Possible spelling mistake found.
Context: ...ig.Codec | |simapp |FundAccount, FundModuleAccount` | Functions moved...


Near line 20: Possible spelling mistake found.
Context: ... | | simapp | FundAccount, FundModuleAccount | Functions moved to x/bank/testutil...


Near line 20: Possible spelling mistake found.
Context: ...FundModuleAccount| Functions moved tox/bank/testutil| |types |AccAddressFromHex` ...


Near line 21: Possible typo: you repeated a whitespace
Context: ...s moved to x/bank/testutil | | types | AccAddressFromHex | `...


Near line 21: Possible spelling mistake found.
Context: ...ed to x/bank/testutil | | types | AccAddressFromHex | `AccAddressFromHexUns...


Near line 21: Possible typo: you repeated a whitespace
Context: ...til| |types |AccAddressFromHex |AccAddressFromHexUnsafe` |...


Near line 21: Possible spelling mistake found.
Context: ... | AccAddressFromHex | AccAddressFromHexUnsafe | | x/auth | `MempoolFee...


Near line 21: Possible typo: you repeated a whitespace
Context: ... | AccAddressFromHexUnsafe | | x/auth | MempoolFeeDecorator ...


Near line 22: Possible typo: you repeated a whitespace
Context: ...ssFromHexUnsafe | |x/auth |MempoolFeeDecorator` | U...


Near line 22: Possible spelling mistake found.
Context: ...omHexUnsafe | |x/auth |MempoolFeeDecorator | UseDeductFeeDecorator...


Near line 22: Possible typo: you repeated a whitespace
Context: ... | | x/auth | MempoolFeeDecorator | Use DeductFeeDecorator instead |...


Near line 22: Possible spelling mistake found.
Context: ...MempoolFeeDecorator | UseDeductFeeDecoratorinstead | |x/bank |AddressFr...


Near line 22: Possible typo: you repeated a whitespace
Context: ... | Use DeductFeeDecorator instead | | x/bank | `AddressFromBalancesStor...


Near line 23: Possible typo: you repeated a whitespace
Context: ...ctFeeDecoratorinstead | |x/bank |AddressFromBalancesStore |...


Near line 23: Possible spelling mistake found.
Context: ...eDecoratorinstead | |x/bank |AddressFromBalancesStore |AddressAndDenomFromBalances...


Near line 23: Possible typo: you repeated a whitespace
Context: ...| x/bank | AddressFromBalancesStore | AddressAndDenomFromBalancesStore |...


Near line 23: Possible spelling mistake found.
Context: ... | AddressFromBalancesStore | AddressAndDenomFromBalancesStore | | x/gov | `keeper.DeleteDeposi...


Near line 23: Possible typo: you repeated a whitespace
Context: ... | AddressAndDenomFromBalancesStore | | x/gov | keeper.DeleteDeposits ...


Near line 24: Possible typo: you repeated a whitespace
Context: ...AndDenomFromBalancesStore | |x/gov |keeper.DeleteDeposits |...


Near line 24: Add a space between sentences.
Context: ...nomFromBalancesStore | |x/gov |keeper.DeleteDeposits |keeper.DeleteAndBurnDepo...


Near line 24: Possible typo: you repeated a whitespace
Context: ... | | x/gov | keeper.DeleteDeposits | keeper.DeleteAndBurnDeposits |...


Near line 24: Add a space between sentences.
Context: ... | keeper.DeleteDeposits | keeper.DeleteAndBurnDeposits | | x/gov | `keeper.RefundDe...


Near line 24: Possible typo: you repeated a whitespace
Context: ... | keeper.DeleteAndBurnDeposits | | x/gov | keeper.RefundDeposits ...


Near line 25: Possible typo: you repeated a whitespace
Context: ...DeleteAndBurnDeposits | |x/gov |keeper.RefundDeposits |...


Near line 25: Add a space between sentences.
Context: ...eAndBurnDeposits | |x/gov |keeper.RefundDeposits |keeper.RefundAndDeleteDe...


Near line 25: Possible typo: you repeated a whitespace
Context: ... | | x/gov | keeper.RefundDeposits | keeper.RefundAndDeleteDeposits |...


Near line 25: Add a space between sentences.
Context: ... | keeper.RefundDeposits | keeper.RefundAndDeleteDeposits | | x/{mod} | package legacy ...


Near line 25: Possible typo: you repeated a whitespace
Context: ... | keeper.RefundAndDeleteDeposits | | x/{mod} | package legacy ...


Near line 26: Possible typo: you repeated a whitespace
Context: ...ts | |x/{mod}| packagelegacy | packagemigrations` |...


Near line 26: Possible typo: you repeated a whitespace
Context: ... | package migrations | For the exhaustive list of API renami...


Near line 30: This sentence does not start with an uppercase letter.
Context: ...smos-sdk/blob/main/CHANGELOG.md). #### new packages Additionally, new packages ha...


Near line 32: Consider a shorter alternative to avoid wordiness.
Context: ...ally, new packages have been introduced in order to further split the codebase. Aliases are...


Near line 34: This sentence does not start with an uppercase letter.
Context: ...grate to this new packages: * errors should replace types/errors when registering...


Near line 35: This sentence does not start with an uppercase letter.
Context: ...errors or wrapping SDK errors. * math contains the Int or Uint types that are used...


Near line 35: Possible spelling mistake found.
Context: ... errors. * math contains the Int or Uint types that are used in the SDK. #### ...


Near line 40: This sentence does not start with an uppercase letter.
Context: ...grant won't expire). * authz.NewGrant takes a new argument: block time, to correctl...


Near line 46: Add a space between sentences.
Context: ...rvice with the gRPC-gateway service via nodeservice.RegisterGRPCGatewayRoutes in their application construction, whi...


Near line 48: Possible spelling mistake found.
Context: ...nstruction, which is typically found in RegisterAPIRoutes. ### Keyring The keyring has been re...


Near line 50: Possible spelling mistake found.
Context: ...ally found in RegisterAPIRoutes. ### Keyring The keyring has been refactored in v0....


Near line 52: Possible spelling mistake found.
Context: ... RegisterAPIRoutes. ### Keyring The keyring has been refactored in v0.46. * The `U...


Near line 54: Possible spelling mistake found.
Context: ...` interfaces have been removed from the keyring package. Please use interface casting i...


Near line 56: This sentence does not start with an uppercase letter.
Context: ...lized as proto. * keyring.NewInMemory and keyring.New takes now a codec.Codec...


Near line 56: Add a space between sentences.
Context: ...d as proto. * keyring.NewInMemory and keyring.New takes now a codec.Codec. * Take `key...


Near line 56: Add a space between sentences.
Context: ...InMemoryandkeyring.Newtakes now acodec.Codec. * Take keyring.Recordinstead ofI...


Near line 57: Add a space between sentences.
Context: ....Newtakes now acodec.Codec. * Take keyring.Recordinstead ofInfo` as first argument in...


Near line 58: Possible spelling mistake found.
Context: ... Info as first argument in: * MkConsKeyOutput * MkValKeyOutput * `...


Near line 59: Possible spelling mistake found.
Context: ...: * MkConsKeyOutput * MkValKeyOutput * MkAccKeyOutput * Rename: ...


Near line 62: Possible spelling mistake found.
Context: ... * MkAccKeyOutput * Rename: * SavePubKey to SaveOfflineKey and remove the `al...


Near line 62: Possible spelling mistake found.
Context: ...ut* Rename: *SavePubKeytoSaveOfflineKeyand remove thealgo` argument. ...


Near line 62: Possible spelling mistake found.
Context: ...KeytoSaveOfflineKeyand remove thealgoargument. *NewMultiInfo, N...


Near line 62: Possible typo: you repeated a whitespace
Context: ...ineKeyand remove thealgoargument. *NewMultiInfo, NewLedgerInfo toN...


Near line 63: Possible spelling mistake found.
Context: ...d remove the algo argument. * NewMultiInfo, NewLedgerInfo to `NewLegacyMultiIn...


Near line 63: Possible spelling mistake found.
Context: ...goargument. *NewMultiInfo, NewLedgerInfo toNewLegacyMultiInfo, newLegacyLe...


Near line 63: Possible typo: you repeated a whitespace
Context: ... * NewMultiInfo, NewLedgerInfo to NewLegacyMultiInfo, `newLegacyLedge...


Near line 63: Possible spelling mistake found.
Context: ... * NewMultiInfo, NewLedgerInfo to NewLegacyMultiInfo, newLegacyLedgerInfo respectively. ...


Near line 63: Possible spelling mistake found.
Context: ...ewLedgerInfo toNewLegacyMultiInfo, newLegacyLedgerInforespectively. *NewOfflineInf...


Near line 63: Possible typo: you repeated a whitespace
Context: ...o, newLegacyLedgerInforespectively. *NewOfflineInfotonewLegacyOfflineI...


Near line 64: Possible spelling mistake found.
Context: ...gacyLedgerInforespectively. *NewOfflineInfotonewLegacyOfflineInfo` and move it ...


Near line 64: Possible spelling mistake found.
Context: ...ectively. * NewOfflineInfo to newLegacyOfflineInfo and move it to migration_test.go. #...


Near line 66: Possible spelling mistake found.
Context: ...nd move it to migration_test.go. ### PostHandler A postHandler is like an `antehandle...


Near line 68: Possible spelling mistake found.
Context: ...migration_test.go. ### PostHandler A postHandleris like anantehandler`, but is run _...


Near line 68: Possible spelling mistake found.
Context: ...PostHandler A postHandler is like an antehandler, but is run after the runMsgs exec...


Near line 68: Possible spelling mistake found.
Context: ...n antehandler, but is run after the runMsgs execution. It is in the same store bra...


Near line 68: Possible spelling mistake found.
Context: ...on. It is in the same store branch that runMsgs, meaning that both runMsgs and `post...


Near line 68: Possible spelling mistake found.
Context: ...ranch that runMsgs, meaning that both runMsgs and postHandler. This allows to run ...


Near line 68: Possible spelling mistake found.
Context: ...nMsgs, meaning that both runMsgsandpostHandler`. This allows to run a custom logic aft...


Near line 70: Possible spelling mistake found.
Context: ...ter the execution of the messages. ### IAVL v0.19.0 IAVL introduces a new "fast" i...


Near line 72: Possible spelling mistake found.
Context: ...ion of the messages. ### IAVL v0.19.0 IAVL introduces a new "fast" index. This ind...


Near line 72: Possible spelling mistake found.
Context: ...ndex represents the latest state of the IAVL laid out in a format that preserves dat...


Near line 80: Possible spelling mistake found.
Context: ...e the following in the logs: "Upgrading IAVL storage for faster queries + execution ...


Near line 84: Possible spelling mistake found.
Context: ...a node operator chooses to downgrade to IAVL pre-fast index, and then upgrade again,...


Near line 91: Possible spelling mistake found.
Context: ...s. ### Modules #### x/params * The x/param module has been depreacted in favour o...


Near line 91: Possible spelling mistake found.
Context: ...arams * Thex/param` module has been depreacted in favour of each module housing and pr...


Near line 91: Possible spelling mistake. ‘favour’ is British English.
Context: ...x/param module has been depreacted in favour of each module housing and providing wa...


Near line 91: Possible spelling mistake found.
Context: ...ach module that has parameters that are changable during runtime have an authority, the a...


Near line 91: Possible spelling mistake found.
Context: ...s migrating modules away from using the param module. An example of how this could lo...


Near line 92: Possible spelling mistake found.
Context: ...m//pull/12363). * The Param module will be maintained until April 1...


Near line 92: It appears that a comma is missing.
Context: ...aintained until April 18, 2023. At this point the module will reach end of life and b...


Near line 97: Consider a shorter alternative to avoid wordiness.
Context: ...the new implementation is called v1. In order to submit a proposal with `submit-proposal...


Near line 98: Possible spelling mistake found.
Context: ...submit-proposalyou now need to pass aproposal.json` file. You can still use the old way by...


Near line 104: The auxiliary verb ‘do’ requires the base form of the verb.
Context: ...v0.45.3/third_party/proto) now does not contains directly the [proto files](https://gith...


Near line 106: Possible spelling mistake found.
Context: ...rd_party/proto). Instead, the SDK uses buf. Clients should ha...


Near line 106: Consider a shorter alternative to avoid wordiness.
Context: ...build/cosmos/cosmos-sdk` as dependency, in order to avoid having to copy paste these files....


Near line 106: Did you mean “copy and paste”?
Context: ...dependency, in order to avoid having to copy paste these files. The protos can as well be...


Near line 108: Possible spelling mistake found.
Context: ... having to copy paste these files. The protos can as well be downloaded using `buf export...


Near line 108: Possible spelling mistake found.
Context: ... protos can as well be downloaded using `buf export buf.build/cosmos/cosmos-sdk:8cb3...

Additional comments not posted (52)
.goreleaser.yml (1)

27-27: Enabling changelog generation is a positive change for maintaining good documentation practices.

.gitignore (2)

26-26: Ignoring the tools/ directory helps keep the repository clean by excluding tool-specific files.


54-54: Ignoring debug_container.dot is appropriate to prevent committing Graphviz output files, which are typically not needed in the source repository.

.github/workflows/lint.yml (3)

20-20: Updating the Go version to 1.19 aligns with the broader update in the development environment.


21-21: Replacing get-diff-action with actions/checkout is a standard and recommended practice for fetching the code in workflows.


26-26: Specifying the golangci-lint version as v1.49.0 ensures consistent linting results across different environments.

.mergify.yml (5)

4-5: Adjusting the base branch conditions for queue rules is a tailored change that likely improves the automation process in the project.


10-12: Configuring pull request rules for automerging with specific conditions enhances the efficiency of the merging process.


16-17: Setting the merge method in the queue actions ensures clarity and consistency in how merges are handled.


20-21: Adjusting the conditions for backporting patches to specific branches helps maintain the stability and continuity of older versions.


28-29: Configuring backport rules with specific labels and branches ensures that patches are correctly applied to relevant versions.

.golangci.yml (2)

14-14: Adding the gofumpt linter is a positive change that enforces more stringent formatting rules, enhancing code readability and consistency.


41-43: Updating exclusion rules for nolintlint helps focus linting efforts on meaningful issues and avoid false positives.

RELEASE_NOTES.md (1)

1-22: The release notes are well-documented, providing clear information on dependency updates and the end-of-life status of the version.

.github/workflows/cosmovisor-release.yml (1)

16-16: Updating the Go version to 1.19 ensures that the latest features and security fixes are used in the workflow.

Dockerfile (1)

13-13: Updating the base image to golang:1.19-alpine ensures compatibility with the latest Golang features and optimizations.

.github/workflows/release.yml (2)

18-18: Update to Go 1.19 is consistent with the PR's objective to update the development environment.


28-45: Ensure the Slack webhook and other secrets are securely managed and not exposed.

Verification successful

The verification process has confirmed that there are no hardcoded secrets, such as the Slack webhook, in the .github/workflows/ directory. The use of ${{ secrets.SLACK_WEBHOOK }} in the workflow file ensures that the secret is securely managed through GitHub Secrets, which is a best practice for handling sensitive information in GitHub Actions.

  • No hardcoded secrets were found in the workflow files.
Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Check for hardcoded secrets which should instead be stored securely.
rg --files-with-matches 'SLACK_WEBHOOK.*[a-zA-Z0-9]{22}' .github/workflows/

Length of output: 77

.github/workflows/codeql-analysis.yml (1)

28-28: Update to Go 1.19 aligns with the broader update to the development environment.

.github/workflows/sims.yml.DISABLED (5)

25-25: Update to Go 1.19 in the 'build' job aligns with the broader update to the development environment.


36-36: Update to Go 1.19 in the 'install-runsim' job aligns with the broader update to the development environment.


54-54: Update to Go 1.19 in the 'test-sim-import-export' job aligns with the broader update to the development environment.


73-73: Update to Go 1.19 in the 'test-sim-after-import' job aligns with the broader update to the development environment.


92-92: Update to Go 1.19 in the 'test-sim-multi-seed-short' job aligns with the broader update to the development environment.

.github/workflows/test-race.yml (4)

27-27: Update to Go 1.19 in the 'install-tparse' job aligns with the broader update to the development environment.


43-43: Update to Go 1.19 in the 'build' job aligns with the broader update to the development environment.


63-63: Update to Go 1.19 in the 'split-test-files' job aligns with the broader update to the development environment.


97-97: Update to Go 1.19 in the 'test-race' job aligns with the broader update to the development environment.

README.md (1)

45-45: Update to Go 1.19+ in the README file aligns with the broader update to the development environment and ensures users are aware of the new requirements.

CHANGELOG-Agoric.md (1)

36-102: Ensure all changelog entries are accurate and follow the specified format. Verify that all links and issue references are correct and functional.

Verification successful

Since the script did not return any matches and the regex was correctly formatted to detect the patterns of GitHub links in the changelog, it is reasonable to conclude that there are no broken links in the CHANGELOG-Agoric.md. Therefore, the changelog entries appear to be accurate in terms of the links and issue references provided.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Check for broken links in the changelog file.
rg --files-with-matches 'https:\/\/github\.com\/[a-zA-Z0-9\-]+\/[a-zA-Z0-9\-]+\/(pull|issues)\/[0-9]+' CHANGELOG-Agoric.md

Length of output: 273



Script:

#!/bin/bash
# Corrected script to check for broken links in the changelog file.
rg --files-with-matches 'https:\\/\\/github\\.com\\/[a-zA-Z0-9\\-]+\\/[a-zA-Z0-9\\-]+\\/(pull|issues)\\/[0-9]+' CHANGELOG-Agoric.md

Length of output: 133

UPGRADING.md (4)

17-27: Ensure consistent formatting in the table of API changes.

The table formatting seems inconsistent with extra spaces. Consider aligning the columns properly to enhance readability.


39-41: Clarify the documentation regarding the new argument in authz.NewGrant.

It would be beneficial to specify what type of "block time" is expected (e.g., timestamp, block number) and provide an example to avoid confusion.


44-49: Ensure the new gRPC service is properly documented.

It's important to provide more details about the new gRPC service introduced. Consider adding a link to the documentation or examples on how to use the new service.


104-108: Clarify the usage of buf for managing proto files.

The transition to using buf for proto management is significant. It would be helpful to include a more detailed guide or link to resources that explain how to set up and use buf.yaml effectively.

SECURITY.md (1)

16-16: Update the URL link for the IAVL library.

The change correctly updates the URL to point to the cosmos repository instead of tendermint, aligning with the current repository structure for the IAVL library.

.github/workflows/test.yml (7)

30-30: Update Go version to 1.19 in the build job.

This change ensures that the build job uses the latest stable version of Go, aligning with best practices for maintaining up-to-date dependencies.


51-51: Update Go version to 1.19 in the test-submodules job.

Consistent updating of the Go version across different jobs ensures that all tests and builds are performed against the same version, reducing the likelihood of version-specific issues.


74-74: Update Go version to 1.19 in the split-test-files job.

Maintaining consistency in the Go version used across various jobs helps in ensuring that the environment remains stable and predictable.


108-108: Update Go version to 1.19 in the tests job.

This update is crucial for ensuring that the tests are run using the latest features and security patches provided by the Go language.


204-204: Update Go version to 1.19 in the liveness-test job.

Updating the Go version for the liveness tests is important to ensure that the tests reflect the current production environment.


227-227: Update Go version to 1.19 in the install-runsim job.

Ensuring that the installation scripts run with the updated Go version helps in avoiding compatibility issues.


244-244: Update Go version to 1.19 in the test-sim-nondeterminism job.

This change ensures that all simulation tests are conducted using the latest Go version, which is critical for catching issues that may not be present in older versions.

RELEASE_PROCESS.md (1)

130-130: Update URLs in Protobuf definitions documentation.

Changing the links from relative to absolute paths enhances the accessibility of the documentation, ensuring that users can reach the relevant resources regardless of where they access the links from.

Makefile (9)

13-14: Update repository URLs to point to the Agoric fork.

This change aligns the build process with the specific needs of the Agoric version of the Cosmos SDK, ensuring that all protocol buffer files and other dependencies are pulled from the correct source.


71-71: Add badgerdb to build tags if specified in build options.

This ensures that the build process correctly includes support for the BadgerDB backend when specified, which is crucial for environments where BadgerDB is used.


76-76: Add rocksdb to build tags if specified in build options.

This addition is necessary to enable RocksDB support in the build process, which is important for performance in certain database operations.


80-80: Add boltdb to build tags if specified in build options.

This change ensures that BoltDB support is correctly included in the build process when specified, catering to environments that utilize BoltDB.


333-338: Update the version of golangci-lint to v1.49.0 and adjust linting commands.

This update ensures that the latest features and fixes of the linter are utilized, improving the code quality checks.


348-351: Introduce gofumpt for code formatting and adjust the formatting command to exclude certain directories and file types.

This addition enhances the code formatting standards by using gofumpt, which enforces a stricter format than gofmt, leading to more consistent and readable code.


397-397: Ensure dependencies are up-to-date after generating protobuf files.

This command is crucial for maintaining the integrity and compatibility of dependencies after any changes to protobuf definitions.


419-419: Check for breaking changes in protobuf files against the Agoric branch of the forked repository.

This is an important addition for maintaining backward compatibility by detecting breaking changes in protobuf files early in the development process.


431-431: Update Protobuf dependencies from a specific version of the Agoric fork.

This command ensures that all Protobuf dependencies are up-to-date, which is crucial for the consistency and reliability of the builds.


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:

Note: Auto-reply has been disabled for this repository by the repository owner. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

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

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.

@JimLarson
Copy link
Contributor Author

Wrong repo.

@JimLarson JimLarson closed this Apr 18, 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: 7

@@ -149,7 +149,7 @@ Pull requests that fix bugs and add features that fall in the following categori
As rule of thumb, the following changes will **NOT** be automatically accepted into stable point-releases:

* **State machine changes**.
* **Protobug-breaking changes**, as specified in [ADR-044](./docs/architecture/adr-044-protobuf-updates- guidelines.md).
* **Protobug-breaking changes**, as specified in [ADR-044](https://github.com/cosmos/cosmos-sdk/blob/main/docs/architecture/adr-044-protobuf-updates- guidelines.md).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarify Protobuf updates guidelines link.

- [ADR-044](https://github.com/cosmos/cosmos-sdk/blob/main/docs/architecture/adr-044-protobuf-updates-       guidelines.md)
+ [ADR-044](https://github.com/cosmos/cosmos-sdk/blob/main/docs/architecture/adr-044-protobuf-updates-guidelines.md)

The URL to the ADR-044 document contains unnecessary spaces, which could lead to a broken link. Correcting this ensures the link is accessible.


Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
* **Protobug-breaking changes**, as specified in [ADR-044](https://github.com/cosmos/cosmos-sdk/blob/main/docs/architecture/adr-044-protobuf-updates- guidelines.md).
* **Protobug-breaking changes**, as specified in [ADR-044](https://github.com/cosmos/cosmos-sdk/blob/main/docs/architecture/adr-044-protobuf-updates-guidelines.md).

Comment on lines +15 to +16
To improve clarity of the API, some renaming and improvements has been done:

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider revising the grammar in the sentence for better clarity.

- To improve clarity of the API, some renaming and improvements has been done:
+ To improve the clarity of the API, some renaming and improvements have been made:

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
To improve clarity of the API, some renaming and improvements has been done:
To improve the clarity of the API, some renaming and improvements have been made:

Comment on lines +30 to +36
#### new packages

Additionally, new packages have been introduced in order to further split the codebase. Aliases are available for a new API breaking migration, but it is encouraged to migrate to this new packages:

* `errors` should replace `types/errors` when registering errors or wrapping SDK errors.
* `math` contains the `Int` or `Uint` types that are used in the SDK.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Capitalize the first letter of bullet points for consistency.

- * `errors` should replace `types/errors` when registering errors or wrapping SDK errors.
- * `math` contains the `Int` or `Uint` types that are used in the SDK.
+ * `Errors` should replace `types/errors` when registering errors or wrapping SDK errors.
+ * `Math` contains the `Int` or `Uint` types that are used in the SDK.

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
#### new packages
Additionally, new packages have been introduced in order to further split the codebase. Aliases are available for a new API breaking migration, but it is encouraged to migrate to this new packages:
* `errors` should replace `types/errors` when registering errors or wrapping SDK errors.
* `math` contains the `Int` or `Uint` types that are used in the SDK.
#### new packages
Additionally, new packages have been introduced in order to further split the codebase. Aliases are available for a new API breaking migration, but it is encouraged to migrate to this new packages:
* `Errors` should replace `types/errors` when registering errors or wrapping SDK errors.
* `Math` contains the `Int` or `Uint` types that are used in the SDK.

Comment on lines +52 to +65
The keyring has been refactored in v0.46.

* The `Unsafe*` interfaces have been removed from the keyring package. Please use interface casting if you wish to access those unsafe functions.
* The keys' implementation has been refactored to be serialized as proto.
* `keyring.NewInMemory` and `keyring.New` takes now a `codec.Codec`.
* Take `keyring.Record` instead of `Info` as first argument in:
* `MkConsKeyOutput`
* `MkValKeyOutput`
* `MkAccKeyOutput`
* Rename:
* `SavePubKey` to `SaveOfflineKey` and remove the `algo` argument.
* `NewMultiInfo`, `NewLedgerInfo` to `NewLegacyMultiInfo`, `newLegacyLedgerInfo` respectively.
* `NewOfflineInfo` to `newLegacyOfflineInfo` and move it to `migration_test.go`.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tip

Codebase Verification

The verification process has revealed the following:

  • The removal of Unsafe* interfaces from the keyring package does not affect other parts of the codebase. The occurrences of "Unsafe" in the codebase are unrelated to the keyring package and are part of different functionalities or configurations.
  • There is no evidence of the correct usage of the new keyring.New($_, $_) method in the codebase. This suggests that the new API might not be integrated properly or at all.

Based on these findings, the following actions are recommended:

  • Ensure that the new keyring.New method is integrated and used correctly throughout the codebase.
Analysis chain

Review the changes in the keyring API for potential breaking changes.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Verify that the removed `Unsafe*` interfaces are not used elsewhere in the codebase.
rg --type go "Unsafe"
# Check for correct usage of the new keyring API.
ast-grep --lang go --pattern $'keyring.New($_, $_)'

Length of output: 13503

Comment on lines +91 to +93
* The `x/param` module has been depreacted in favour of each module housing and providing way to modify their parameters. Each module that has parameters that are changable during runtime have an authority, the authority can be a module or user account. The Cosmos-SDK team recommends migrating modules away from using the param module. An example of how this could look like can be found [here](https://github.com/cosmos/cosmos-sdk/pull/12363).
* The Param module will be maintained until April 18, 2023. At this point the module will reach end of life and be removed from the Cosmos SDK.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct the spelling mistake and add a comma for clarity.

- * The `x/param` module has been depreacted in favour of each module housing and providing way to modify their parameters.
+ * The `x/param` module has been deprecated in favor of each module housing and providing a way to modify their parameters.
- * The Param module will be maintained until April 18, 2023. At this point the module will reach end of life and be removed from the Cosmos SDK.
+ * The Param module will be maintained until April 18, 2023. At this point, the module will reach end of life and be removed from the Cosmos SDK.

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
* The `x/param` module has been depreacted in favour of each module housing and providing way to modify their parameters. Each module that has parameters that are changable during runtime have an authority, the authority can be a module or user account. The Cosmos-SDK team recommends migrating modules away from using the param module. An example of how this could look like can be found [here](https://github.com/cosmos/cosmos-sdk/pull/12363).
* The Param module will be maintained until April 18, 2023. At this point the module will reach end of life and be removed from the Cosmos SDK.
* The `x/param` module has been deprecated in favor of each module housing and providing a way to modify their parameters. Each module that has parameters that are changable during runtime have an authority, the authority can be a module or user account. The Cosmos-SDK team recommends migrating modules away from using the param module. An example of how this could look like can be found [here](https://github.com/cosmos/cosmos-sdk/pull/12363).
* The Param module will be maintained until April 18, 2023. At this point, the module will reach end of life and be removed from the Cosmos SDK.

Comment on lines +3 to +35
- `Agoric` - the trunk for our cosmos-sdk fork, used by [agoric-sdk](https://github.com/Agoric/agoric-sdk).
- New features which we plan to use in a near-future release are added here.
- Most releases are tagged here.
- `Agoric-vX.Y.Z-alpha.agoric.A.x` - a lazily-created release branch.
- Branched off of release tag `vX.Y.Z-alpha.agoric.A`.
- Created when we need a new release that omits some changes present on trunk.
- Prefer to contain only cherry-picks from trunk.
- Pattern can be extended to sub-sub-branches should the need arise.

Tag convention:

- `vX.Y.Z-alpha.agoric.A` for tagged releases on the `Agoric` branch:
- `vX.Y.Z` is the version of the latest integrated cosmos/cosmos-sdk release.
- The `A` is an increasing sequence resetting to `1` after the integration of a new cosmos/cosmos-sdk release.
- `vX.Y.Z-alpha.agoric.A.B` for "patch" releases on branch `Agoric-vX.Y.Z-alpha.agoric.A.x`.
- `B` starts at 1 and increases sequentially.
- Pattern can be extended to releases on sub-sub-branches should the need arise.

For new features:

- New features should be landed on `Agoric` first, then cherry-picked to a release branch as needed.
- Create a new development branch off of `Agoric`.
- Test, review, merge PR with `automerge` label for mergify.io
- Don't forget to update `CHANGELOG-Agoric.md` with the change and a link to its PR.

Upon new cosmos-sdk releases, see [upgrading the Interchain Stack](https://github.com/Agoric/agoric-sdk/wiki/Upgrading-the-Interchain-Stack).

Historical work:
- [ag0](https://github.com/Agoric/ag0) [Agoric mainnet](https://agoric.com)
phase 0's [gaiad-equivalent](https://github.com/cosmos/gaia)
- `Agoric-ag0` - should be identical to
[cosmos/cosmos-sdk](https://github.com/cosmos/cosmos-sdk) + changes needed by
`ag0`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct spelling mistakes and grammatical errors to enhance the clarity and professionalism of the document.

- lazily-created
+ lazily created
- Branched off of
+ Branched from
- vX.Y.Z-alpha.agoric.A.x
+ vX.Y.Z-alpha.agoric.A.x

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
- `Agoric` - the trunk for our cosmos-sdk fork, used by [agoric-sdk](https://github.com/Agoric/agoric-sdk).
- New features which we plan to use in a near-future release are added here.
- Most releases are tagged here.
- `Agoric-vX.Y.Z-alpha.agoric.A.x` - a lazily-created release branch.
- Branched off of release tag `vX.Y.Z-alpha.agoric.A`.
- Created when we need a new release that omits some changes present on trunk.
- Prefer to contain only cherry-picks from trunk.
- Pattern can be extended to sub-sub-branches should the need arise.
Tag convention:
- `vX.Y.Z-alpha.agoric.A` for tagged releases on the `Agoric` branch:
- `vX.Y.Z` is the version of the latest integrated cosmos/cosmos-sdk release.
- The `A` is an increasing sequence resetting to `1` after the integration of a new cosmos/cosmos-sdk release.
- `vX.Y.Z-alpha.agoric.A.B` for "patch" releases on branch `Agoric-vX.Y.Z-alpha.agoric.A.x`.
- `B` starts at 1 and increases sequentially.
- Pattern can be extended to releases on sub-sub-branches should the need arise.
For new features:
- New features should be landed on `Agoric` first, then cherry-picked to a release branch as needed.
- Create a new development branch off of `Agoric`.
- Test, review, merge PR with `automerge` label for mergify.io
- Don't forget to update `CHANGELOG-Agoric.md` with the change and a link to its PR.
Upon new cosmos-sdk releases, see [upgrading the Interchain Stack](https://github.com/Agoric/agoric-sdk/wiki/Upgrading-the-Interchain-Stack).
Historical work:
- [ag0](https://github.com/Agoric/ag0) [Agoric mainnet](https://agoric.com)
phase 0's [gaiad-equivalent](https://github.com/cosmos/gaia)
- `Agoric-ag0` - should be identical to
[cosmos/cosmos-sdk](https://github.com/cosmos/cosmos-sdk) + changes needed by
`ag0`
- `Agoric` - the trunk for our cosmos-sdk fork, used by [agoric-sdk](https://github.com/Agoric/agoric-sdk).
- New features which we plan to use in a near-future release are added here.
- Most releases are tagged here.
- `Agoric-vX.Y.Z-alpha.agoric.A.x` - a lazily created release branch.
- Branched from release tag `vX.Y.Z-alpha.agoric.A`.
- Created when we need a new release that omits some changes present on trunk.
- Prefer to contain only cherry-picks from trunk.
- Pattern can be extended to sub-sub-branches should the need arise.
Tag convention:
- `vX.Y.Z-alpha.agoric.A` for tagged releases on the `Agoric` branch:
- `vX.Y.Z` is the version of the latest integrated cosmos/cosmos-sdk release.
- The `A` is an increasing sequence resetting to `1` after the integration of a new cosmos/cosmos-sdk release.
- `vX.Y.Z-alpha.agoric.A.B` for "patch" releases on branch `Agoric-vX.Y.Z-alpha.agoric.A.x`.
- `B` starts at 1 and increases sequentially.
- Pattern can be extended to releases on sub-sub-branches should the need arise.
For new features:
- New features should be landed on `Agoric` first, then cherry-picked to a release branch as needed.
- Create a new development branch off of `Agoric`.
- Test, review, merge PR with `automerge` label for mergify.io
- Don't forget to update `CHANGELOG-Agoric.md` with the change and a link to its PR.
Upon new cosmos-sdk releases, see [upgrading the Interchain Stack](https://github.com/Agoric/agoric-sdk/wiki/Upgrading-the-Interchain-Stack).
Historical work:
- [ag0](https://github.com/Agoric/ag0) [Agoric mainnet](https://agoric.com)
phase 0's [gaiad-equivalent](https://github.com/cosmos/gaia)
- `Agoric-ag0` - should be identical to
[cosmos/cosmos-sdk](https://github.com/cosmos/cosmos-sdk) + changes needed by
`ag0`

Comment on lines +4 to +9
- New features which we plan to use in a near-future release are added here.
- Most releases are tagged here.
- `Agoric-vX.Y.Z-alpha.agoric.A.x` - a lazily-created release branch.
- Branched off of release tag `vX.Y.Z-alpha.agoric.A`.
- Created when we need a new release that omits some changes present on trunk.
- Prefer to contain only cherry-picks from trunk.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adjust the indentation of unordered list items for consistency and readability.

-    - New features which we plan to use in a near-future release are added here.
+  - New features which we plan to use in a near-future release are added here.
-    - Most releases are tagged here.
+  - Most releases are tagged here.

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
- New features which we plan to use in a near-future release are added here.
- Most releases are tagged here.
- `Agoric-vX.Y.Z-alpha.agoric.A.x` - a lazily-created release branch.
- Branched off of release tag `vX.Y.Z-alpha.agoric.A`.
- Created when we need a new release that omits some changes present on trunk.
- Prefer to contain only cherry-picks from trunk.
- New features which we plan to use in a near-future release are added here.
- Most releases are tagged here.
- `Agoric-vX.Y.Z-alpha.agoric.A.x` - a lazily-created release branch.
- Branched off of release tag `vX.Y.Z-alpha.agoric.A`.
- Created when we need a new release that omits some changes present on trunk.
- Prefer to contain only cherry-picks from trunk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.