-
Notifications
You must be signed in to change notification settings - Fork 95
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 3.7.4 #701
Release 3.7.4 #701
Conversation
Related to #688 , I tested
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can update the CHANGELOG, I forgot to put the 653 into the changelog in the past:
diff --git a/CHANGELOG.md b/CHANGELOG.md
index fa565d5..c15edb7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -5,9 +5,15 @@ All notable changes to this crate are documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this crate adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-## Unreleased
+## 3.7.4 - 2025-02-05
-### [3.7.3] - 2025-01-30
+### Added
+
+- Disallow duplicate indexes using constant evaluation ([#653](https://github.com/paritytech/parity-scale-codec/pull/653))
+
+## [3.7.3] - 2025-01-30
+
+### Added
- Fix added bounds in `Encode` and other derive macros. ([#689](https://github.com/paritytech/parity-scale-codec/pull/689))
Note that if we run cargo test we can some error:
people will have to update |
I am not sure yet. People will complain that frame-support
doesn't compile. Maybe we should update frame-support
first.
Done |
Yes, you're right. We should patch frame-support probably |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also checked compilation of open-runtime-module-library.
Looks good to me.
No description provided.