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 2.4.0 #175

Merged
merged 4 commits into from
Mar 23, 2023
Merged

Release 2.4.0 #175

merged 4 commits into from
Mar 23, 2023

Conversation

lexnv
Copy link
Contributor

@lexnv lexnv commented Mar 23, 2023

Added

  • portable: Retain the provided type IDs (#174)

// CC @paritytech/tools-team

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
@lexnv lexnv requested review from ascjones and jsdw March 23, 2023 12:58
@lexnv lexnv self-assigned this Mar 23, 2023
@jsdw
Copy link
Contributor

jsdw commented Mar 23, 2023

I think 2.4 makes more sense given semver; crates depending on eg "2.3" should still automatically be happy to use this :)

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
@jsdw
Copy link
Contributor

jsdw commented Mar 23, 2023

Ooh also, it feels like the derive crate is generally kept in line (perhaps that was missed with the latest patch release), so I wonder whether we should bump that to the same? @ascjones any opinions?

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
@lexnv
Copy link
Contributor Author

lexnv commented Mar 23, 2023

I've also bumped the scale-info-derive crate to v2.4, it seems a bit more inline with how we release subxt crates. Will wait for @ascjones to confirm if this makes sense here, thanks!

@lexnv lexnv changed the title Release 2.3.2 Release 2.4.0 Mar 23, 2023
@lexnv lexnv merged commit 842114e into master Mar 23, 2023
@lexnv lexnv deleted the lexnv/release_2.3.2 branch March 23, 2023 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants