-
Notifications
You must be signed in to change notification settings - Fork 633
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
CI: Pin cargo-public-api version #2893
CI: Pin cargo-public-api version #2893
Conversation
541a5b1
to
e2365f4
Compare
So that updates don't break our CI setup used a specific version of `cargo-public-api`, this means we will have to update it manually periodically though. For now, since the latest release just broke us, use the release from a month ago.
e2365f4
to
7e3b2eb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 7e3b2eb
@@ -317,6 +317,6 @@ jobs: | |||
with: | |||
toolchain: ${{ needs.Prepare.outputs.nightly_version }} | |||
- name: "Install cargo-public-api" | |||
run: cargo install --locked cargo-public-api | |||
run: cargo install cargo-public-api@0.35.0 --locked |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why change the order? I'm surprised it even works. Usually switches go before positional arguments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would guess that as long as everything is after install
it'll work in any order.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh woops I just cut and pasted it from the docs at some stage while I was playing with it, I should not have included that change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in #2900
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 7e3b2eb
So that updates don't break our CI setup used a specific version of
cargo-public-api
, this means we will have to update it manually periodically though.For now, since the latest release just broke us, use the release from a month ago.