v0.6.3

Fix

• commands/install.py: avoid f-string unmatched error on Python < 3.12

---

🔐 Verifying the artifacts

All release artifacts (executables and packages for every OS) are included in the signed checksums.txt file.

How to verify:

1. Download checksums.txt, checksums.txt.sig, and checksums.txt.pem from the release.
2. Run this command:

cosign verify-blob \
  --cert checksums.txt.pem \
  --signature checksums.txt.sig \
  --certificate-identity "https://github.com/CPToolset/xcsp-launcher/.github/workflows/release.yml@refs/heads/main" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  checksums.txt

If the output is Verified OK, you can then validate the integrity of the downloaded files:

sha256sum --ignore-missing -c checksums.txt

v0.6.2

Fix

• utils/path.py: Fixes the search path for installation with homebrew

---

🔐 Verifying the artifacts

All release artifacts (executables and packages for every OS) are included in the signed checksums.txt file.

How to verify:

1. Download checksums.txt, checksums.txt.sig, and checksums.txt.pem from the release.
2. Run this command:

cosign verify-blob \
  --cert checksums.txt.pem \
  --signature checksums.txt.sig \
  --certificate-identity "https://github.com/CPToolset/xcsp-launcher/.github/workflows/release.yml@refs/heads/main" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  checksums.txt

If the output is Verified OK, you can then validate the integrity of the downloaded files:

sha256sum --ignore-missing -c checksums.txt

v0.6.1

v0.6.1 (2025-08-12)

Fix

• builder/build.py: Fixes a bug with the build part of a solver

---

🔐 Verifying the artifacts

All release artifacts (executables and packages for every OS) are included in the signed checksums.txt file.

How to verify:

1. Download checksums.txt, checksums.txt.sig, and checksums.txt.pem from the release.
2. Run this command:

cosign verify-blob \
  --cert checksums.txt.pem \
  --signature checksums.txt.sig \
  --certificate-identity "https://github.com/CPToolset/xcsp-launcher/.github/workflows/release.yml@refs/heads/main" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  checksums.txt

If the output is Verified OK, you can then validate the integrity of the downloaded files:

sha256sum --ignore-missing -c checksums.txt

v0.6.0

• Refactor/build system and config file
  • PR: #2
• Feat/detect latest version
  • PR: #3

---

🔐 Verifying the artifacts

All release artifacts (executables and packages for every OS) are included in the signed checksums.txt file.

How to verify:

1. Download checksums.txt, checksums.txt.sig, and checksums.txt.pem from the release.
2. Run this command:

cosign verify-blob \
  --cert checksums.txt.pem \
  --signature checksums.txt.sig \
  --certificate-identity "https://github.com/CPToolset/xcsp-launcher/.github/workflows/release.yml@refs/heads/main" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  checksums.txt

If the output is Verified OK, you can then validate the integrity of the downloaded files:

sha256sum --ignore-missing -c checksums.txt

v0.5.1

• no changes

---

🔐 Verifying the artifacts

All release artifacts (executables and packages for every OS) are included in the signed checksums.txt file.

How to verify:

1. Download checksums.txt, checksums.txt.sig, and checksums.txt.pem from the release.
2. Run this command:

cosign verify-blob \
  --cert checksums.txt.pem \
  --signature checksums.txt.sig \
  --certificate-identity "https://github.com/CPToolset/xcsp-launcher/.github/workflows/release.yml@refs/heads/main" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  checksums.txt

If the output is Verified OK, you can then validate the integrity of the downloaded files:

sha256sum --ignore-missing -c checksums.txt

v0.4.0

• no changes

---

🔐 Verifying the artifacts

All release artifacts (executables and packages for every OS) are included in the signed checksums.txt file.

How to verify:

1. Download checksums.txt, checksums.txt.sig, and checksums.txt.pem from the release.
2. Run this command:

cosign verify-blob \
  --cert checksums.txt.pem \
  --signature checksums.txt.sig \
  --certificate-identity "https://github.com/CPToolset/xcsp-launcher/.github/workflows/release.yml@refs/heads/main" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  checksums.txt

If the output is Verified OK, you can then validate the integrity of the downloaded files:

sha256sum --ignore-missing -c checksums.txt

v0.3.0

Full Changelog: v0.2.1...v0.3.0

---

🔐 Verifying the artifacts

All release artifacts (executables and packages for every OS) are included in the signed checksums.txt file.

How to verify:

1. Download checksums.txt, checksums.txt.sig, and checksums.txt.pem from the release.
2. Run this command:

cosign verify-blob \
  --cert checksums.txt.pem \
  --signature checksums.txt.sig \
  --certificate-identity "https://github.com/CPToolset/xcsp-launcher/.github/workflows/release.yml@refs/heads/main" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  checksums.txt

If the output is Verified OK, you can then validate the integrity of the downloaded files:

sha256sum --ignore-missing -c checksums.txt

v0.2.1

• no changes

---

🔐 Verifying the artifacts

All release artifacts (executables and packages for every OS) are included in the signed checksums.txt file.

How to verify:

1. Download checksums.txt, checksums.txt.sig, and checksums.txt.pem from the release.
2. Run this command:

cosign verify-blob \
  --cert checksums.txt.pem \
  --signature checksums.txt.sig \
  --certificate-identity "https://github.com/CPToolset/xcsp-launcher/.github/workflows/release.yml@refs/heads/main" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  checksums.txt

If the output is Verified OK, you can then validate the integrity of the downloaded files:

sha256sum --ignore-missing -c checksums.txt

v0.2.0

• no changes

---

🔐 Verifying the artifacts

All release artifacts (executables and packages for every OS) are included in the signed checksums.txt file.

How to verify:

1. Download checksums.txt, checksums.txt.sig, and checksums.txt.pem from the release.
2. Run this command:

cosign verify-blob \
  --cert checksums.txt.pem \
  --signature checksums.txt.sig \
  --certificate-identity "https://github.com/CPToolset/xcsp-launcher/.github/workflows/release.yml@refs/heads/main" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  checksums.txt

If the output is Verified OK, you can then validate the integrity of the downloaded files:

sha256sum --ignore-missing -c checksums.txt

v0.1.1

Full Changelog: v0.1.0...v0.1.1

---

🔐 Verifying the artifacts

All release artifacts (executables and packages for every OS) are included in the signed checksums.txt file.

How to verify:

1. Download checksums.txt, checksums.txt.sig, and checksums.txt.pem from the release.
2. Run this command:

cosign verify-blob \
  --cert checksums.txt.pem \
  --signature checksums.txt.sig \
  --certificate-identity "https://github.com/CPToolset/xcsp-launcher/.github/workflows/release.yml@refs/heads/main" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  checksums.txt

If the output is Verified OK, you can then validate the integrity of the downloaded files:

sha256sum --ignore-missing -c checksums.txt