From e007b8118eaa38f9b470187c8568f95d80fe15c8 Mon Sep 17 00:00:00 2001 From: Daniel Larraz Date: Fri, 4 Sep 2026 16:45:48 -0500 Subject: [PATCH] Build cvc5 as an unrestricted build cvc5/cvc5#12899 renamed the build types configure.sh accepts and made selecting one mandatory: production became unrestricted, safe-mode became safe, and stable-mode became stable. The old names are rejected outright rather than silently ignored, so the build step now fails at once: *** configure.sh: build type 'production' is no longer available. Use 'unrestricted' to have the previous behavior. The step that checks out cvc5 names no ref, so it takes the default branch, and the artifact cache is keyed on the SHA it resolves to. The build therefore runs on every cvc5 commit, and CI has been broken since the rename landed. Use the new name. It is the same build, just spelled differently, so nothing else has to change. The cache keys track $CVC5_CONFIG, so this invalidates the cvc5 artifact and dependency caches once. The next run repopulates them. Co-authored-by: Claude Opus 5 (1M context) --- .github/workflows/ci.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 6775f98..200787f 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -9,7 +9,7 @@ jobs: # The configuration cvc5 is built with. The cache keys below track this # value instead of the workflow file, so that unrelated changes to the # workflow do not invalidate the cached artifacts. - CVC5_CONFIG: production --auto-download --python-bindings --cocoa --gpl + CVC5_CONFIG: unrestricted --auto-download --python-bindings --cocoa --gpl # cancel already running jobs for the same branch/pr/tag concurrency: