Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v0.41.0 #176

Merged
merged 4 commits into from
Jan 9, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions .changelog/unreleased/features/167-ics721-impl.md

This file was deleted.

2 changes: 2 additions & 0 deletions .changelog/v0.41.0/features/167-ics721-impl.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
- Add ICS-721 NFT transfer application proto types
([\#167](https://github.com/cosmos/ibc-proto-rs/issues/167)).
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
- Integrate Wasm light client proto types by updating `IBC_GO_COMMIT` to the
hash associated with the ibc-go `wasm-v8.0.0` tag
([#168](https://github.com/cosmos/ibc-proto-rs/issues/168)).
([\#168](https://github.com/cosmos/ibc-proto-rs/issues/168)).
6 changes: 6 additions & 0 deletions .changelog/v0.41.0/summary.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
*January 9th, 2024*

This release integrates the ICS-08 Wasm light client and ICS-721 NFT transfer
application proto types. It additionally resolves the removal of the `#[no_std]`
attribute, introduces the `informalsystems-pbjson/std` dependency for std
feature compatibility.
22 changes: 22 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,27 @@
# CHANGELOG

## v0.41.0

*January 9th, 2024*

This release integrates the ICS-08 WASM light client and ICS-721 NFT transfer
application proto types. It additionally resolves the removal of the `#[no_std]`
attribute, introduces the `informalsystems-pbjson/std` dependency for std
feature compatibility.

### BUG FIXES

- Fix `#[no_std]` attribute removal and add `informalsystems-pbjson/std` dependency
for `std` feature ([\#171](https://github.com/cosmos/ibc-proto-rs/issues/171)).

### FEATURES

- Add ICS-721 NFT transfer application proto types
([\#167](https://github.com/cosmos/ibc-proto-rs/issues/167)).
- Integrate WASM light client proto types by updating `IBC_GO_COMMIT` to the
hash associated with the ibc-go `wasm-v8.0.0` tag
([\#168](https://github.com/cosmos/ibc-proto-rs/issues/168)).

## v0.40.0

*December 29th, 2023*
Expand Down
16 changes: 9 additions & 7 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -225,8 +225,8 @@ Our release process is as follows:
1. Running `unclog build -u` and copy pasting the output at the top
of the `CHANGELOG.md` file, making sure to update the header with
the new version.
1. Running `unclog release vX.Y.Z` to create a summary of all of the changes
in this release.
2. Running `unclog release --version vX.Y.Z --editor <editor>` to create a
summary of all of the changes in this release.
3. Committing the updated `CHANGELOG.md` file and `.changelog` directory to the repo.
2. Push this to a branch `release/vX.Y.Z` according to the version number of
the anticipated release (e.g. `release/v0.18.0`) and open a **draft PR**.
Expand All @@ -243,19 +243,21 @@ Our release process is as follows:
7. Checkout the `main` and pull it with `git checkout main && git pull origin main`.
Then create a signed tag and push it to GitHub: `git tag -s -a vX.Y.Z && git push origin vX.Y.Z`
In the tag message, write the version and the link to the corresponding section of the changelog.
9. If any problem arises, submit a new PR, get it merged to `main` and try again.
8. If any problem arises, submit a new PR, get it merged to `main` and try again.
The reason for not releasing straight from the release branch, and therefore losing the
ability to fix publishing-related problems as they arise, is that we would like the embedded
metadata of the published crates, namely the Git commit at which the release was done,
to match the Git commit on the `main` branch which will be tagged.
[See this article][crates.io-security] for a more in-depth explanation.
**Note:** This step requires the appropriate privileges to push crates to [crates.io].
10. Once the tag is pushed, wait for the CI bot to create a GitHub release,
then update the release description to
```
9. Once the tag is pushed, wait for the CI bot to create a GitHub release, then
update the release description to

```md
[📖 CHANGELOG](https://github.com/cosmos/ibc-proto-rs/blob/master/CHANGELOG.md#vXYZ)`
```
11. All done! 🎉

10. All done! 🎉

[crates.io]: https://crates.io
[crates.io-security]: https://codeandbitters.com/published-crate-analysis/
2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "ibc-proto"
version = "0.40.0"
version = "0.41.0"
authors = ["Informal Systems <[email protected]>"]
edition = "2021"
license = "Apache-2.0"
Expand Down
Loading