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

ci(semver-checks): avoid stale caches after rustc or tool upgrade #3664

Merged
merged 4 commits into from
Mar 24, 2023

Conversation

thomaseizinger
Copy link
Contributor

Description

With an upgrade to the Rust toolchain, the version of the rustdoc JSON may change. We incorporate the rustc version into the cache key to automatically invalidate the cache in that case. Additionally, we also incorporate the version of the cargo semver-checks tool.

Related: obi1kenobi/cargo-semver-checks#415.

Notes & open questions

Change checklist

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • A changelog entry has been made in the appropriate crates

This should avoid the cache getting stale with changes in rustdoc
format.
@thomaseizinger thomaseizinger requested a review from mxinden March 22, 2023 21:50
@thomaseizinger thomaseizinger changed the title ci(semver-checks): avoid stale caches after rustc upgrade ci(semver-checks): avoid stale caches after rustc or tool upgrade Mar 22, 2023
Copy link
Member

@mxinden mxinden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Limited expertise with the setup. Looks good to me.

@mergify mergify bot merged commit 82e38bf into master Mar 24, 2023
@mergify mergify bot deleted the fix/version-semver-checks-cache-with-rust-version branch March 24, 2023 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants