-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Fix caching in release-dry-run #1419
Labels
github_actions
Pull requests that update GitHub Actions code
Comments
Just moving the cargo-binstall and the minisign, rage installation before the caching would fix it. |
It also happened in release-dry-run for other targets. I think the problem is that it's picking up old cache which doesn't habe rage and minisign installed in release-build |
NobodyXu
added a commit
that referenced
this issue
Sep 28, 2023
Fixed #1419 Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 29, 2023
* Fix `release-packages` and `release-cli` workflow Fixed #1419 Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com> * Use `taiki-e/install-action` for `rsign2` & `rage` in `release-packages.yml` Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com> --------- Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that somehow it caches the installed crates manifest but does not cache rsign2, causing our CI to fail.
The text was updated successfully, but these errors were encountered: