-
Notifications
You must be signed in to change notification settings - Fork 97
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
Proposing: v1.2.4 Release #288
Comments
Cherry pick #286 onto the 1.2.2 release for a clean 1.2.3 release. This release is the one proposed in #288 The changelog from main is clipped to only include the relevant changes from the cherry picked commit. - A migration is added to onboard the people chain without the usual two sale boundary delay that came with the shift to coretime. - Another migration is added to clean up an outdated assignment in state from the old sale start before the leases were added. More info in the changelog of this PR and PR #286. - [ ] Does not require a CHANGELOG entry --------- Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com>
Edit: Will come with 1.2.5 |
Just in case the intention is to include all runtimes in the release. Kusama Coretime should not be bumped without this PR. |
Yeah with the |
To facilitate moving bridged assets around the ecosystem. |
@joepetrowski, Maybe? Honestly it's a perfect match for other XCM related PRs, and how it is right now, it's small enough not to require immense amounts of testing (I've done some tests myself of how this might work using Chopsticks). We can then make the same modification for similar chains in the future. |
To fix Snowbridge Ethereum consensus updates being rejected and resets the Ethereum client checkpoint. |
Would like to propose following to be added to v1.2.4 Contains the following updates: |
PR here: #318 |
@joepetrowski you can close this |
Based on the discussion in the last Fellowship call about smaller patch releases and holding off on v1.3.0 for Coretime, I would propose the following:
v1.2.3 (Coretime only)
v1.2.4
system::authorize_upgrade
in XCM #280I think this could be a parachains-only release, although the Ambassador Program might involve modifying the Fellowship Admin track on the Relay Chain.
Note: We actually need to be careful not to upgrade the Kusama Relay Chain until the People Chain is live, because the Identity Reaper (now guarded by Root) will become open, and it needs a parachain to send to.
The text was updated successfully, but these errors were encountered: