-
Notifications
You must be signed in to change notification settings - Fork 381
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
Runtime-1000 release prep #1377
Conversation
/runtime-upgrade-test shibuya,shiden,astar |
Invalid runtime. It should be 'shibuya', 'shiden', or 'astar'. |
/runtime-upgrade-test shibuya |
Runtime upgrade test is scheduled at https://github.com/AstarNetwork/Astar/actions/runs/11557218702. |
@Dinonard maybe we wait for this backport? |
Sure, we can wait. However, I'd like to see this on SHibuya ASAP since we plan to upgrade Shiden next Monday. |
/runtime-upgrade-test shibuya |
Runtime upgrade test is scheduled at https://github.com/AstarNetwork/Astar/actions/runs/11558465739. |
Runtime upgrade test finished: yarn run v1.22.22 RUN v2.0.5 /home/runner/work/Astar/Astar/tests/e2e ✓ tests/runtime-upgrade.test.ts (1 test) 48723ms Test Files 1 passed (1) Done in 55.66s. |
Minimum allowed line rate is |
/runtime-upgrade-test shiden |
Runtime upgrade test is scheduled at https://github.com/AstarNetwork/Astar/actions/runs/11572398290. |
@Dinonard Chopsticks needs to be updated for this test to work |
Haven't checked the results by now, but it makes sense. |
Summary
Prepare for the first runtime release.
Spec versions are bumped according to the new versioning schema.
Crates are bumped as well, but this might need to be revised later on since it might make things more confusing due to the overlap with the client version.