Repository navigation
Tags
Tags
version.h: the version a consumer can assert, ahead of the v0.1.0 tag
The Tap family roadmap's A9 (SampleRateTap docs/ROADMAP.md). DspTap
declared its version only in project(DspTap VERSION 0.1.0) and had no tag,
so a consumer pinned a bare SHA and could not state which DspTap it was
tested with.
- include/tap/dsp/version.h: TAP_DSP_VERSION_MAJOR/_MINOR/_PATCH (0.1.0),
TAP_DSP_VERSION_ENCODE(major, minor, patch) and TAP_DSP_VERSION, packed
(major << 16) | (minor << 8) | patch like the family's C ABI version
probes, so a floor compares in #if and static_assert alike.
- tests/test_version.cpp: Version.HeaderMatchesTheProjectVersion pins the
header to project()'s version (passed in from CMake), and
Version.EncodingIsBitPackedAndOrdered pins the packing and its order.
Both run in tap_dsp_tests, so every leg runs them.
- README "Versioning" and CLAUDE.md's release flow state the rule:
- bump project() and version.h together, and tag the commit vX.Y.Z;
- tag on this repo's own cadence, never in lockstep with a consumer;
- consumers assert the oldest DspTap they were tested with, and name
the tag in the commit that moves their pin.
Once this merges, v0.1.0 tags the merge commit on main. SampleRateTap then
moves its pin there and asserts the floor in each engine's umbrella header.
Locally, with clang 18 Release: the full battery passes (506 of 506,
expects.PublicHeadersCompileWithoutExceptions included, which compiles the
new header under -fno-exceptions), and clang-tidy and clang-format are clean.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016GKzq1VSdcMYCRMhddiMaf