Skip to content

chore(release): 0.13.0 - #269

Merged
SizzleUnrlsd merged 5 commits into
mainfrom
chore/release-0.13.0
Nov 17, 2026
Merged

SizzleUnrlsd merged 5 commits into
mainfrom
chore/release-0.13.0

Conversation

@SizzleUnrlsd

@SizzleUnrlsd SizzleUnrlsd commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Change

Prepares the 0.13.0 release.

scripts/ci/semver_check.py computes 0.13.0 from the commits since v0.12.0: a minor bump, as two are feat commits, 52e9d06 (#262) and 897f321 (#265), and none has a breaking-change marker.

Public compatibility, checked

  • cc options and runtime ABI. git diff v0.12.0 origin/main -- include/coretrace is empty, and src/compilerlib/args.cpp adds or removes no --ct-* option.
  • compilerlib headers. compilerlib/compile_module.hpp is new (feat(compilerlib): compile to an llvm::Module in the caller's context #265). compilerlib/compiler.h changes in its comments only (feat(compilerlib): give each compilation a working directory of its own #262). compilerlib/frontend/no_instrument_action.hpp and optnone_action.hpp now include the new no_instrument_consumer.hpp and optnone_consumer.hpp, which hold the declarations they had (perf: speed up compilerlib's build and instrumentation passes #251).
  • One behaviour of compile: with -working-directory, the process stays where it is unless a job runs as a program (feat(compilerlib): give each compilation a working directory of its own #262). It is listed under Behaviour changes.
  • Linking across versions (macOS arm64, LLVM 20.1.2). ct_leak_site.c, ct_double_free_site.c, ct_new_delete.cpp and ct_vtable_basic.cpp, compiled by one version and linked with the runtime of the other through CT_RUNTIME_LIB_DIR, run as when both are the same version: same exit status, and the same output once addresses and process ids are replaced, with the leak lines, the double free line, the new and delete traces, the vtable boxes and value=2. The 0.13.0 side is main at 61f88b5.
  • README: a search for the issues fixed since 0.12.0 found no statement to bring up to date; the README was not read through for this.

Before merge

After merge

Create the v0.13.0 tag and release on the merge commit of this PR. The release notes cover the 24 pull requests merged since v0.12.0: #220 to #222, #228 to #230, #234, #235, #238 to #242, #245 to #248, #250, #251, #254, #255, #260, #262 and #265.

The Unreleased section becomes v0.13.0, with a summary, a compatibility
statement and the known issues. Each entry that cited its issue alone
also cites its pull request.
The summary of v0.13.0 says that the leaks are reported at process exit,
and that the runtime state is freed when the DLL is dynamically
unloaded.

Refs #269
The section of v0.13.0 is dated 2026-11-17, the day the release is
published.

Refs #269
@SizzleUnrlsd
SizzleUnrlsd marked this pull request as ready for review November 17, 2026 18:42
@SizzleUnrlsd
SizzleUnrlsd merged commit e213053 into main Nov 17, 2026
40 of 41 checks passed
@SizzleUnrlsd
SizzleUnrlsd deleted the chore/release-0.13.0 branch November 17, 2026 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore Codebase maintenance: cleanup, formatting, build/CI tweaks, and minor internal updates.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant