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

upgrade to polkadot sdk stable2409 #469

Open
acatangiu opened this issue Oct 4, 2024 · 3 comments · Fixed by #490
Open

upgrade to polkadot sdk stable2409 #469

acatangiu opened this issue Oct 4, 2024 · 3 comments · Fixed by #490

Comments

@acatangiu
Copy link
Contributor

Aiming to upgrade the fellowship repo to new SDK once every three months, that way we can keep a balance between when things are released in the SDK and when they are deployed on system chains.

I suggest we skip 2407 at this point and upgrade straight to 2409 (it includes everything in 2407 anyway).

@hqwangningbo
Copy link
Contributor

@acatangiu Is anyone else working on this and if not I can offer my help to speed up the process.

@acatangiu
Copy link
Contributor Author

@hqwangningbo nobody is working on it, help would be appreciated!

@pandres95
Copy link
Contributor

pandres95 commented Oct 18, 2024

@acatangiu on it. 🫡

Expect PR draft next Monday.

fellowship-merge-bot bot pushed a commit that referenced this issue Dec 12, 2024
Closes #457 
Closes #469

Updating the runtimes to SDK version `stable2409-1`. CHANGELOG mentions
all relevant changes for UI and Walletbuilders.

## Checklist

- [x] Update SDK to `stable2409`
- [x] Update configuration for relay chains.
- [x] Update configuration for system parachains.
- [x] Update configuration for emulated chains.
- [x] Update configuration for Encointer (see _Help wanted_).
- [x] Update CHANGELOG.
- [x] Update SDK to `stable2409-1`

## Dependencies

This PR depends on certain PRs to be merged before it can properly work.

- [x] #472

## Impacts

The success of this PR impacts directly on the feasibility of executing
certain issues, or closing certain PRs.

- [ ] #455
- [ ] #476
- [ ] #480
- [ ] #484

## Help wanted

Initially, I request the help of:

- @franciscoaguirre to help me correcting the potential conflicts that
may arise when foreign assets change to `XCMv4`.
- @acatangiu to help me setting up the Bridge Hubs, as well as adding
the respective transition layer (a.k.a. preparing the migrations from
fixed `Lanes` to `LegacyLane`-based lanes storage).
- @clangenb to help me upgrading Encointer.
- @Szegoo to check the parameters that changed in Coretime.

---------

Co-authored-by: clangenb <[email protected]>
Co-authored-by: Clara van Staden <[email protected]>
Co-authored-by: Ankan <[email protected]>
Co-authored-by: Dónal Murray <[email protected]>
Co-authored-by: Branislav Kontur <[email protected]>
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 a pull request may close this issue.

3 participants