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

Fix TestLocalToolchain jobs for release push #3131

Merged
merged 1 commit into from
Apr 6, 2024

Conversation

tautschnig
Copy link
Member

Upon pushing a release tag, we use the numeric version instead of "latest", which made kani-latest a non-existent folder. See https://github.com/model-checking/kani/actions/runs/8574249138 for such an example. Use the version variable instead, which will be set to "latest" or the numeric version as appropriate.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

Upon pushing a release tag, we use the numeric version instead of
"latest", which made `kani-latest` a non-existent folder. See
https://github.com/model-checking/kani/actions/runs/8574249138 for such
an example. Use the `version` variable instead, which will be set to
"latest" or the numeric version as appropriate.
@tautschnig tautschnig requested a review from a team as a code owner April 5, 2024 20:12
@tautschnig tautschnig merged commit 5490933 into model-checking:main Apr 6, 2024
23 checks passed
@tautschnig tautschnig deleted the fix-release-test-job branch April 6, 2024 06:54
zpzigi754 pushed a commit to zpzigi754/kani that referenced this pull request May 8, 2024
Upon pushing a release tag, we use the numeric version instead of
"latest", which made `kani-latest` a non-existent folder. See
https://github.com/model-checking/kani/actions/runs/8574249138 for such
an example. Use the `version` variable instead, which will be set to
"latest" or the numeric version as appropriate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants