diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 86d8e9e..ad35a74 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -53,20 +53,6 @@ jobs: - run: cmake -S . -B build -DCMAKE_C_COMPILER=clang -DTXMS_SANITIZE=ON -DTXMS_FUZZ=ON - run: cmake --build build -j2 - run: build/txms_fuzz tests/corpus -runs=20000 -max_len=2048 - conan: - strategy: - matrix: - os: [ubuntu-latest, macos-latest, windows-latest] - shared: ['False', 'True'] - runs-on: ${{ matrix.os }} - steps: - - uses: actions/checkout@v4 - - uses: actions/setup-python@v5 - with: - python-version: '3.12' - - run: python -m pip install 'conan>=2.12,<3' - - run: conan profile detect --force - - run: conan create . --build=missing --no-remote -o "libtxms/*:shared=${{ matrix.shared }}" release-tooling: runs-on: ubuntu-latest steps: diff --git a/README.md b/README.md index fb9e446..f59b56f 100644 --- a/README.md +++ b/README.md @@ -88,17 +88,16 @@ conan install --requires=libtxms/0.1.0 --build=missing -g CMakeDeps -g CMakeTool Consumers use `find_package(txms CONFIG REQUIRED)` and link `txms::txms`. Conan packages include the CORE license and attribution. Packaging recipes and the standalone `test_package` are MIT licensed under [packaging/LICENSE](packaging/LICENSE); -the library remains CORE licensed. `shared` and `fPIC` are supported. CI builds -static/shared packages on Linux, macOS and Windows; Windows packaging checks -run in hosted CI and have not been executed locally. +the library remains CORE licensed. `shared` and `fPIC` are supported. The recipe is available for +manual local use; Conan packaging tests do not run in CI. ## GitHub releases [release.yml](.github/workflows/release.yml) starts when a stable GitHub Release is **published**, using tags such as `0.1.0` without a `v` prefix. It calls the complete CI workflow at the tagged commit, including sanitizers, compatibility -tests, fuzz checks and Conan consumer tests. The release is already visible while -tests run; assets are attached only after all tests and package checks pass. +tests and fuzz checks. The release is already visible while +tests run; assets are attached only after all CI tests pass. 1. Update `CMakeLists.txt`, commit the version/workflow changes and push them. 2. Create and publish a GitHub Release for the matching tag, such as `0.1.0`,