Skip to content

Bump CI to Rustc 1.88 to support 2024 edition crates #8592

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

Merged
merged 46 commits into from
Jul 4, 2025
Merged

Bump CI to Rustc 1.88 to support 2024 edition crates #8592

merged 46 commits into from
Jul 4, 2025

Conversation

jsdw
Copy link
Contributor

@jsdw jsdw commented May 21, 2025

As one example, this allows us to use the latest version of Subxt: 0.42. Also if-let chains :)

Main changes:

  • Update CI image
  • Remove forklift from Build step in check-revive-stable-uapi-polkavm; it seemed to cause an error. Perhaps we can open an issue for this to fix/try again after this merges.
  • Bump polkavm deps to 0.26 to avoid this error (thanks @koute!)
  • Add result_large_err clippy to avoid a bunch of clippy warnings about a 176 byte error (again, we could fix this later more properly).
  • Clippy fixes (mainly inlining args into format!s where possible), remove one #[no_mangle] on a #[panic_hook] and a few other misc automatic fixes.
  • #[allow(clippy::useless_conversion)] in frame macro to avoid the generated .map(Into::into).map_err(Into::into) code causing an issue when not necessary (it is sometimes; depends on the return type in pallet calls)
  • UI test updates

As a side note, I haven't added a prdoc since I'm not making any breaking changes (despite touching a bunch of pallets), just clippy/fmt type things. Please comment if this isn't ok!

Also, thankyou @bkchr for the wasmtime update PR which fixed a blocker here!

@jsdw jsdw added the R0-no-crate-publish-required The change does not require any crates to be re-published. label May 21, 2025
@jsdw jsdw marked this pull request as ready for review May 21, 2025 11:03
@jsdw jsdw requested review from a team as code owners May 21, 2025 11:03
@jsdw jsdw changed the title Bump CI to Rustc 1.85 to support 2024 edition crates [WIP] Bump CI to Rustc 1.85 to support 2024 edition crates May 21, 2025
@AndWeHaveAPlan
Copy link
Contributor

There is a request to update 'taplo' in 'ci-unified'. An updated image with rust 1.85 is on the way. I'll add an update with a new image tag when it's published

@jsdw jsdw requested a review from a team as a code owner May 21, 2025 12:58
@jsdw jsdw marked this pull request as draft May 21, 2025 13:00
@jsdw jsdw added the A5-run-CI Run CI on draft PR label May 21, 2025
@jsdw jsdw changed the title [WIP] Bump CI to Rustc 1.85 to support 2024 edition crates Bump CI to Rustc 1.85 to support 2024 edition crates May 21, 2025
Co-authored-by: Evgeny Snitko <evgeny@parity.io>
@jsdw jsdw enabled auto-merge July 4, 2025 11:39
@paritytech-workflow-stopper
Copy link

All GitHub workflows were cancelled due to failure one of the required jobs.
Failed workflow url: https://github.com/paritytech/polkadot-sdk/actions/runs/16072927716
Failed job name: cargo-clippy

@jsdw jsdw disabled auto-merge July 4, 2025 13:01
@jsdw
Copy link
Contributor Author

jsdw commented Jul 4, 2025

@bkchr are you happy with things here now? If so I think we're ready now to merge :)

@jsdw jsdw added this pull request to the merge queue Jul 4, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 4, 2025
@jsdw jsdw added this pull request to the merge queue Jul 4, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 4, 2025
@bkchr bkchr added this pull request to the merge queue Jul 4, 2025
@jsdw
Copy link
Contributor Author

jsdw commented Jul 4, 2025

The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

I saw this a couple of times now so assuming some GitHub issue but fingers crossed it's intermittent enough that it'll not happen after a few retries!

@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 4, 2025
@jsdw jsdw added this pull request to the merge queue Jul 4, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 4, 2025
@jsdw jsdw added this pull request to the merge queue Jul 4, 2025
Merged via the queue into master with commit 771c998 Jul 4, 2025
246 of 247 checks passed
@jsdw jsdw deleted the jsdw-1.85 branch July 4, 2025 22:31
@jsdw
Copy link
Contributor Author

jsdw commented Jul 4, 2025

13th time lucky 😁

sigurpol pushed a commit that referenced this pull request Jul 8, 2025
As one example, this allows us to use the latest version of Subxt: 0.42.
Also if-let chains :)

Main changes:
- Update CI image
- Remove `forklift` from Build step in
`check-revive-stable-uapi-polkavm`; it seemed to [cause an
error](https://github.com/paritytech/polkadot-sdk/actions/runs/16004536662/job/45148002314?pr=8592).
Perhaps we can open an issue for this to fix/try again after this
merges.
- Bump `polkavm` deps to 0.26 to avoid [this
error](https://github.com/paritytech/polkadot-sdk/actions/runs/16004991577/job/45150325849?pr=8592#step:5:1967)
(thanks @koute!)
- Add `result_large_err` clippy to avoid a bunch of clippy warnings
about a 176 byte error (again, we could fix this later more properly).
- Clippy fixes (mainly inlining args into `format!`s where possible),
remove one `#[no_mangle]` on a `#[panic_hook]` and a few other misc
automatic fixes.
- `#[allow(clippy::useless_conversion)]` in frame macro to avoid the
generated `.map(Into::into).map_err(Into::into)` code causing an issue
when not necessary (it is sometimes; depends on the return type in
pallet calls)
- UI test updates

As a side note, I haven't added a `prdoc` since I'm not making any
breaking changes (despite touching a bunch of pallets), just clippy/fmt
type things. Please comment if this isn't ok!

Also, thankyou @bkchr for the wasmtime update PR which fixed a blocker
here!

---------

Co-authored-by: Evgeny Snitko <evgeny@parity.io>
Co-authored-by: Bastian Köcher <git@kchr.de>
@jsdw jsdw added the A4-backport-stable2506 Pull request must be backported to the stable2506 release branch label Jul 16, 2025
@paritytech-release-backport-bot

Created backport PR for stable2506:

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-8592-to-stable2506
git worktree add --checkout .worktree/backport-8592-to-stable2506 backport-8592-to-stable2506
cd .worktree/backport-8592-to-stable2506
git reset --hard HEAD^
git cherry-pick -x 771c9988e2a636a150d97c10e3122af8068d1687
git push --force-with-lease

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A4-backport-stable2506 Pull request must be backported to the stable2506 release branch A5-run-CI Run CI on draft PR R0-no-crate-publish-required The change does not require any crates to be re-published.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants