-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add version number to registered #658
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Few small things, but looks good.
Can you also add the "Bump spec_version
" label to the PR?
CHANGELOG.md
Outdated
@@ -20,11 +20,12 @@ At the moment this project **does not** adhere to | |||
`StakingExtensionConfigproactive_refresh_data` and takes a tuple of `Vec`. Both should be empty at | |||
genesis for production. | |||
- In [#631](https://github.com/entropyxyz/entropy-core/pull/631), the `config_interface` field of `ProgramInfo` was renamed to `interface_description` to be more semantically accurate. This field will now be used to describe program interfaces, including the auxilary and configuration interfaces of the program. | |||
- In [#658](https://github.com/entropyxyz/entropy-core/pull/658), `RegisteredInfo` and `RegisteredInfo` now contain `version_number` |
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.
- In [#658](https://github.com/entropyxyz/entropy-core/pull/658), `RegisteredInfo` and `RegisteredInfo` now contain `version_number` | |
- In [#658](https://github.com/entropyxyz/entropy-core/pull/658), `RegisteredInfo` and `RegisteringDetails` now contain `version_number` |
You'll also need to make a note of the new KeyVersionNumber
config parameter.
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.
In the change log? doesn't that not touch outside interactions so should remain off the breaking changes
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.
@JesseAbram if any external developer were to use our pallet, they would need to know about this
Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
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.
💯 Good move.
Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
Closes #646