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

Version 4.8.2 - substrate 0.9.31 #167

Closed
wants to merge 4 commits into from
Closed

Version 4.8.2 - substrate 0.9.31 #167

wants to merge 4 commits into from

Conversation

rakanalh
Copy link
Contributor

@rakanalh rakanalh commented Nov 27, 2023

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.

  • Change version to 4.8.2
  • Update spec and transaction versions
    • Update cere-dev
    • Update cere

@rakanalh rakanalh mentioned this pull request Nov 27, 2023
5 tasks
@@ -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,
Copy link
Contributor Author

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,
Copy link
Contributor Author

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,
Copy link
Contributor Author

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,
Copy link
Contributor Author

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

@MRamanenkau
Copy link
Contributor

We use Git Flow as a branching strategy.
Is there a reason to change it?

@rakanalh
Copy link
Contributor Author

@MRamanenkau I am aware of gitflow... could you elaborate on what i am missing?

@rakanalh rakanalh closed this Nov 28, 2023
@rakanalh rakanalh deleted the version-4.8.2 branch November 28, 2023 09:43
@MRamanenkau MRamanenkau restored the version-4.8.2 branch March 18, 2024 12:20
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.

3 participants