router
router copied to clipboard
chore(deps): update rust docker tag to v1.63.0
This PR contains the following updates:
| Package | Update | Change |
|---|---|---|
| rust | minor | 1.63.0 -> 1.64.0 |
| rust | minor | 1.61.0 -> 1.64.0 |
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
â™» Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
- [ ] If you want to rebase/retry this PR, click this checkbox. âš Warning: custom changes will be lost.
This PR has been generated by Mend Renovate. View repository job log here.
@renovate[bot] your pull request is missing a changelog!
Two things:
-
The linker is still getting (presumably OOM) killed on the
linuxbuilds. -
Non-Linux builds are exhibiting:
error: you are deriving `PartialEq` and can implement `Eq` --> uplink/src/lib.rs:16:10 | 16 | #[derive(GraphQLQuery)] | ^^^^^^^^^^^^ | = note: `-D clippy::derive-partial-eq-without-eq` implied by `-D warnings` = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#derive_partial_eq_without_eq = note: this error originates in the derive macro `GraphQLQuery` (in Nightly builds, run with -Z macro-backtrace for more info) error: could not compile `apollo-uplink` due to previous error warning: build failed, waiting for other jobs to finish... error: could not compile `apollo-uplink` due to previous error Error: cargo command failed
Second one doesn't seem worrying, but the first is going to take time.
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above.
âš Warning: custom changes will be lost.
@renovate[bot], please add a /NEXT_CHANGELOG.md entry for this PR to the appropriate section!