build(deps): Bump cosmossdk.io/log from 0.1.1-0.20230329182155-367f0dc1194d to 1.0.0

[dependabot]

Bumps cosmossdk.io/log from 0.1.1-0.20230329182155-367f0dc1194d to 1.0.0.

Release notes

Sourced from cosmossdk.io/log's releases.

Cosmovisor v1.0.0 Release Notes

This is the first major release of Cosmovisor. It changes the way Cosmovisor is searching for an upgrade event from an app. Instead of scanning standard input and standard output logs, the Cosmovisor observes the $DAEMON_HOME/upgrade-info.json file, that is produced by the x/upgrade module. The upgrade-info.json files is created by the x/upgrade module and contains information from the on-chain upgrade Plan record. Using the file based approach solved many outstanding problems: freezing when logs are too long, race condition with the x/upgrade handler, and potential exploit (if a chain would allow to log an arbitrary message, then an attacker could produce a fake upgrade signal and halt a chain or instrument a download of modified, hacked binary when the auto download option is enabled).

Auto downloads

Cosmovisor v1.0 supports auto downloads based on the information in the data/upgrade-info.json. In the Cosmos SDK < v0.44, that file doesn't contain upgrade.Plan.Info, that is needed for doing auto download. Hence Cosmovisor v1.0 auto download won't work with Apps updating from v0.43 and earlier.

NOTE: we don't recommend using auto download functionality. It can lead to potential chain halt when the upgrade Plan contains a bad link or the resource with the binary will be temporarily unavailable. We are planning on adding a upgrade verification command which can potentially solve this issue.

Other updates

• Changed default value of DAEMON_RESTART_AFTER_UPGRADE to true.
• Added version command, which prints both the Cosmovisor and the associated app version.
• Added help command, which prints the Cosmovisor help without passing it to the associated version. This is an exception, because normally, Cosmovisor passes all arguments to the associated app.

For more details, please see the CHANGELOG.

DB v1.0.0-beta.1

github.com/cosmos/cosmos-sdk/db (cosmos-sdk/db here an after) is a module in the Cosmos SDK repository. It is used in store/v2 instead of tendermint/tm-db which is now deprecated. cosmos-sdk/db extends the tendermint/tm-db interface. however, it only supports BaggerDB and RocksDB (the databases we tested, which provide snapshot functionality necessary for store/v2 and ADR-040 implementation).

v0.47.1

Cosmos SDK v0.47.1 Release Notes

💬 Release Discussion

📝 Changelog

Check out the changelog for an exhaustive list of changes, or compare changes from last release.

Refer to the upgrading guide when migrating from v0.46.x to v0.47.0.

🚀 Highlights

This is the first patch release for the v0.47.x line. Missed the v0.47.0 announcement? Read it here.

It includes sweet things we could not include in v0.47.0 due to the feature freeze.

Notably, it introduces a new x/group query for listing of all groups on a chain and a x/gov helper function for commands to use when the command is for submitting a governance proposal.

v0.47.0

Cosmos SDK v0.47.0 Release Notes

✨ Official Release Announcement

💬 Release Discussion

📝 Changelog

... (truncated)

Changelog

Sourced from cosmossdk.io/log's changelog.

Changelog

[Unreleased]

Features

• (x/bank) #15265 Update keeper interface to include GetAllDenomMetaData.
• (client) #15458 Add a CmdContext field to client.Context initialized to cobra command's context.
• (core) #15133 Implement RegisterServices in the module manager.
• (x/gov) #14373 Add new proto field constitution of type string to gov module genesis state, which allows chain builders to lay a strong foundation by specifying purpose.
• (x/genutil) #15301 Add application genesis. The genesis is now entirely managed by the application and passed to CometBFT at note instantiation. Functions that were taking a cmttypes.GenesisDoc{} now takes a genutiltypes.AppGenesis{}.
• (cli) #14659 Added ability to query blocks by events with queries directly passed to Tendermint, which will allow for full query operator support, e.g. >.
• (x/gov) #14720 Upstream expedited proposals from Osmosis.
• (x/auth) #14650 Add Textual SignModeHandler. It is however NOT enabled by default, and should only be used for TESTING purposes until SIGN_MODE_TEXTUAL is fully released.

... (truncated)

Commits

• See full diff in compare view

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)