Skip to content

v1.9.6

Latest

Choose a tag to compare

@github-actions github-actions released this 20 Nov 01:36
· 3 commits to develop since this release

This release is all fixes. If your workflows use @v1 or @v1.9, they already have them.

  • Retired runners: GitHub retired the macos-14 image, but cpp-matrix kept sending Apple Clang 15 jobs there, and GitHub cancelled them right away. It now uses only the runner labels that GitHub Docs lists as supported.
  • The wrong compiler: when the requested version wasn't installed, the setup actions could keep one that didn't match. For example, clang-cl 23 ran the runner image's clang 20. They now skip it and install the right version. clang-cl also gets the MSVC developer environment it needs to link.
  • GCC on older Ubuntu: setup-gcc now adds the ubuntu-toolchain-r/test PPA, so GCC 15 and 16 install on ubuntu:20.04 without extra apt setup. A failed add-apt-repository no longer leaves behind an unsigned source that breaks the next apt-get update.
  • Test failures: cmake-workflow no longer ignores failing tests when run-tests is unset.
  • Release notes: create-changelog keeps the paragraphs and word breaks of commit message bodies in footnotes, and reads footers only from the last paragraph.

Thanks to @Nerixyz for the cmake-workflow fix and @gennaroprota for the create-changelog fixes.

πŸ› Fixes

Bug fixes and error corrections

  • cmake-workflow: Unchecked test failures when run-tests is unset. f404cfb (thanks @Nerixyz)
  • create-changelog:
  • cpp-matrix: Runners retired from GitHub Actions.6 152fe02
  • package-install:
    • Programs that do not satisfy the requested version.7 7d5a603
    • Chocolatey and Homebrew lookups of paths with spaces.8 978119f
  • setup-cpp: MSVC environment for clang-cl.9 3030759
  • setup-gcc:
    • PPA source left by a failed add-apt-repository.10 fe44df8
    • GCC versions newer than the Ubuntu archive from the ubuntu-toolchain-r test PPA.11 6d96501

πŸ§ͺ Tests

Test cases and testing-related changes

  • Coverage of files no test imports.12 c67c66c
  • Code the coverage change revealed in setup-program, update-data, release and process-coverage.13 5fc4a4e
  • Code the coverage change revealed in create-changelog.14 16db028

🚦 Continuous Integration

Changes related to continuous integration

  • MacOS-Clang 23 without dependencies.15 d898d3a
  • Push trigger for branch names with a slash.16 0a6f66e

πŸ—οΈ Chores

Routine tasks, maintenance, and housekeeping

Parent release: v1.9.5 456b4c6

  1. Any body line starting with "word: " or containing "word #" was taken for a footer, so prose such as "object: ctx.corpus..." or "Closes issue #1146." showed up as "(object: ...)" and "(issue: issue #1146.)". Footers are now read only from the message's last paragraph, and only when every line of it is a trailer; the regex is anchored as a whole, and "Closes issue #N" is read as "Closes #N".

    Footnotes joined body lines with nothing in between, fusing the words across the break ("thatis"). They are joined with a space now. ↩

  2. The footnotes in the release notes hold the commit message bodies, and we flattened each body onto one line by deleting its newlines. That glued the last word of every line to the first word of the next, so a body like word1 word2\nword3 word4 showed up as word1 word2word3 word4.

    We now replace each newline, along with the whitespace around it, with a single space. ↩

  3. The parser dropped the blank lines of a commit message, so a body with several paragraphs reached its release-note footnote as one paragraph.

    The parser now records a blank line inside the body as a paragraph break, and the footnote indents every paragraph after the first by four spaces, which is how GitHub Markdown continues a footnote across paragraphs. ↩

  4. When two commits share a type, scope and description, we merge the second into the first and append its body. The bodies were concatenated with nothing in between, so the footnote ran the last word of one body into the first word of the next.

    We now put a paragraph break between them. ↩

  5. Create-changelog.py still deleted the newlines of a commit message body when writing its footnote, the bug that "fix(create-changelog): join footnote lines with a space" fixed in the action. ↩

  6. GitHub retired the macos-14 image from GitHub Actions on November 2, 2026, but actions/runner-images still has its toolset (Azure DevOps runs it until November 23), so update-data kept it and cpp-matrix kept sending Apple Clang 15 there. Every such job was cancelled at once with "The configuration 'macos-14-arm64-us-default' is not supported".

    Update-data now reads the runner labels GitHub Actions accepts from the GitHub Docs table of hosted runners and leaves out every runner image that is not among them, in runner-images.json and in the suffixed Windows runners windows-msvc-defaults.json finds on its own. The labels are saved in runner-images.json as supported_labels.

    Cpp-matrix no longer names runners the data can answer for: - The runner that hosts Ubuntu containers is the oldest Ubuntu runner in runner-images.json instead of ubuntu-22.04, and a release older than it gets a container unless GitHub still has a runner for that release (ubuntu-18.04 and ubuntu-20.04 entries ran on retired runners). - The Visual Studio generator inferred from runs-on comes from the runner's toolsets in windows-msvc-defaults.json. - When the data is missing, the fallbacks are macos-latest and windows-latest.

    Tests that pinned values of the data files now take their expectations from those files, so they hold after each data update. ↩

  7. FindProgramInPaths kept a program that failed the version check as its result, with version null, whenever nothing better had been found. Callers that check only the path took it as found: setup-clang and setup-gcc skip their Homebrew and Chocolatey steps when a path is set. On Windows, clang-cl 23 found the image's clang 20.1.8 and never installed LLVM 23:.

    C:\Program Files\LLVM\bin\clang++.exe does not satisfy requirement 23 findProgramInSystemPaths: Found clang++ version null in C:\Program Files\LLVM\bin\clang++.exe.

    The build then failed against the image's MSVC STL, which requires Clang 22 or newer. Clang-CL 22 had been running on clang 20 the same way and passed only because the older STL accepted it. MinGW and the macOS GCC and Clang installs had the same problem.

    A program that does not satisfy the version is now skipped, as the function's documentation already said. ↩

  8. FindProgramWithChoco and findProgramWithBrew passed the binary path to exec.getExecOutput unquoted. @actions/exec parses that argument as a command line and splits it at spaces, so on Windows checking C:\Program Files\LLVM\bin\clang-cl.exe ran "C:\Program" and threw. Even right after Chocolatey installed LLVM 23, the lookup reported:.

    FindProgramWithChoco: Binary C:\Program Files\LLVM\bin\clang-cl.exe not executable or errored.

    And clang-cl setup failed. The paths are now quoted with escapePath, as the vcpkg and git calls already do, and the lookup logs the error it caught. ↩

  9. Setup-cpp set up clang-cl through setup-clang alone, without the MSVC developer environment. Clang-cl compiles and links with MSVC's headers, libraries and tools, so CMake's compiler check failed at the link step, with no manifest tool found:.

    C:\Strawberry\c\bin\cmake.exe -E vs_link_exe ..--mt=CMAKE_MT-NOTFOUND ..MT: command "CMAKE_MT-NOTFOUND /nologo /manifest ..." failed.

    This never showed in CI because the Clang-CL entry was running plain clang.exe from the runner image (GNU-like command line) instead of the requested clang-cl, until package-install stopped returning programs that did not satisfy the requested version.

    Clang-cl now activates the MSVC environment (any toolset) through setup-msvc before setting up clang, like msvc does; the outputs still describe clang-cl. ↩

  10. Add-apt-repository can fail after writing the PPA's source file. In the GCC 9 job (ubuntu:20.04 container), downloading the ubuntu-toolchain-r PPA's signing key timed out:.

    Error: retrieving gpg key timed out. ##[warning]add-apt-repository failed with exit code 1. GCC versions from the ubuntu-toolchain-r PPA may not be available.

    Setup-gcc only warned, but the unsigned source stayed in /etc/apt/sources.list.d, and the next apt-get update, in package-install, failed the job:.

    E: The repository 'http://ppa.launchpad.net/ubuntu-toolchain-r/ppa/ubuntu focal InRelease' is not signed.

    Setup-gcc now lists /etc/apt/sources.list.d before running add-apt-repository and, when it fails, removes the files that appeared, so the failure stays a warning. The files are removed directly because add-apt-repository --remove looks the PPA up on Launchpad again. ↩

  11. Setup-gcc added ppa:ubuntu-toolchain-r/ppa, which publishes nothing for focal and nothing newer than GCC 14 for later releases, so GCC 15 on ubuntu:20.04 was never found and workflows had to add the test PPA's apt source themselves. The test PPA has every GCC newer than each release's archive (GCC 11 to 16 for focal). ↩

  12. CollectCoverageFrom was only set inside each project config, where Jest ignores it, so a source file that no test imported never showed up in the coverage report. Adding the first test that imports such a file made all of its old uncovered code count at once and broke the threshold (PR #36: git-parsing.ts, 160 uncovered branches against a threshold of 8).

    The option is now global, so every source file is measured from the start. The thresholds of the directories that had untested files are set to the new counts plus 2. A threshold of 0 turned out to disable the check rather than require full coverage, so directories with uncovered code no longer use 0. ↩

  13. Collecting coverage from every source file showed code that no test had ever loaded. These tests cover it, and the thresholds of those directories go down to the counts that remain, plus the usual 2:.

    Setup-program 520 β†’ 1 uncovered statements utils/update-data 359 β†’ 11 utils/release 263 β†’ 2 process-coverage 180 β†’ 1 common/pretty-errors 30 β†’ 0 utils/esbuild 1 β†’ 0.

    What remains cannot be reached: a branch every caller rules out, a fallback after a value that is never null, an output directory created right after a file was read from it. A directory with nothing uncovered gets -2 rather than 0, because 0 turns the check off.

    The tests mock git, npm, downloads, the GitHub API and the file system, and build expected paths with path.join, so they pass on Linux, macOS and Windows. One test is it.failing: macos-xcode-defaults reads "Xcode_14.3.1.app" as version "14.3.1.", a bug outside this change. ↩

  14. Collecting coverage from every source file showed create-changelog code that no test had ever loaded: the action entry point, the CLI, the GitHub API client, most of the git parsing and the input schema. These tests cover it, and the create-changelog threshold goes down from 712 to 1 uncovered statement, plus the usual 2. The statement left, a continue in removeCommitDuplicates, cannot be reached.

    These tests come after the create-changelog fixes because they check their output (footnote paragraphs, merged bodies). They mock git, the GitHub API and the file system, so they pass on Linux, macOS and Windows.

    One test records current behavior that looks wrong, outside this change: getLocalCommits drops the oldest commit of the git log output, so a log with only "feat: a" gives no commits. ↩

  15. With LLVM 23 now installed for macOS-Clang, the Boost.Variant2 tests that include Boost.JSON fail to compile. Boost.Move and Boost.Container forward-declare std types inside libc++'s _LIBCPP_BEGIN_NAMESPACE_STD, which in LLVM 23 also pushes function attributes that those class declarations never use, and Variant2's tests turn the warning into an error:.

    ./boost/container/detail/std_fwd.hpp:55:1: error: unused attribute 'visibility' in '#pragma clang attribute push' region [-Werror,-Wpragma-clang-attribute].

    MacOS-Clang 23 and later entries now get No-Deps, like MinGW, until boostorg/move#67 is fixed. A forced No-Deps entry has no factors, so the B2 workflow, which always builds against the cloned Boost, now also skips No-Deps entries, and Boost is no longer cloned for them. ↩

  16. The push filter '*' does not match '/', so branches such as fix/setup-gcc-toolchain-test-ppa never ran CI on push. '**' matches every branch. ↩

  17. Runner images without macos-14 (retired from GitHub Actions) and with ubuntu-26.04, current Xcode, MSVC, MinGW and LLVM versions, compiler and CMake tags, Ubuntu compiler defaults, and the Boost 1.92.0 dependency graph. ↩