-
Notifications
You must be signed in to change notification settings - Fork 3
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
Version 4.8.2 - substrate 0.9.31 #167
Conversation
@@ -123,10 +123,10 @@ pub const VERSION: RuntimeVersion = RuntimeVersion { | |||
// and set impl_version to 0. If only runtime | |||
// implementation changes and behavior does not, then leave spec_version as | |||
// is and increment impl_version. | |||
spec_version: 48009, | |||
spec_version: 48010, |
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.
Cere: increment spec version
impl_version: 0, | ||
apis: RUNTIME_API_VERSIONS, | ||
transaction_version: 6, | ||
transaction_version: 7, |
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.
Cere: increment transaction version
impl_version: 0, | ||
apis: RUNTIME_API_VERSIONS, | ||
transaction_version: 6, | ||
transaction_version: 7, |
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.
Cere-dev: increment transaction version
@@ -129,10 +129,10 @@ pub const VERSION: RuntimeVersion = RuntimeVersion { | |||
// and set impl_version to 0. If only runtime | |||
// implementation changes and behavior does not, then leave spec_version as | |||
// is and increment impl_version. | |||
spec_version: 48015, | |||
spec_version: 48016, |
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.
Cere-dev: increment spec version
We use Git Flow as a branching strategy. |
@MRamanenkau I am aware of gitflow... could you elaborate on what i am missing? |
This is a PR that should precede #146 to be able to tag this 4.8.2 release prior to merging the 0.9.33 PR.