cmakefmt/cmakefmt - CodSpeed

cmakefmt

Blog Docs Changelog

Performance History

Latest Results

main

8 hours ago

docs(cli): correct "two tree views" wording in dump section header Trivial follow-up to bbde979. The "Parse Tree Dump" section header intro said `cmakefmt dump` provides "two tree views" — that was accurate before v1.6.0 but stale after `dump spec-coverage` landed, which is a coverage-report view (not a tree view) but still under the `dump` namespace. Updated to "three introspection views: two tree views (`ast`, `parse`) and one registry coverage report (`spec-coverage`)." Renaming the section to something like "Inspection Subcommands" would more accurately match the broader scope but would force anchor changes in cross-references; keep "Parse Tree Dump" for backwards compatibility with existing links. `behavior.md` mentions `dump ast` / `dump parse` in a formatter-debugging context and intentionally doesn't mention `spec-coverage` — that's not a source-tree introspection tool. No update there.

main

9 hours ago

docs(changelog): record v1.6.0 expansion items Adds Unreleased entries for the four post-initial-scope items that landed before the v1.6.0 cut: - `Fixed` — playground at cmakefmt.dev reliably reflects the released version after a tag push (Phase 60 WASM-at-tag). - `Internal` — `cargo-fuzz` harness with parse and format_roundtrip targets, advisory weekly CI (Phase 58). - `Internal` — exit-code rendering unified through `render_cli_error` for `run_config_subcommand` and `install_git_hook` (Phase 63 polish). - `Internal` — `comments_playground_preset` megablob snapshot split into five focused tests (Phase 58 cleanup). The cargo-fuzz harness and exit-code unification are CI/internal strictly, but both have user-experience implications worth recording: the fuzz harness is a new safety-net surface for contributors, and the exit-code unification means every error from the binary now has the same envelope shape (machine consumers parsing stderr see one canonical format, not two). The snapshot split is pure cleanup but worth recording so the next reviewer understands why the megablob disappeared. docs/src/content/docs/changelog.md mirrored via `scripts/sync-changelog.py`.

main

9 hours ago

Merge pull request #61 from cmakefmt/refactor/main-rs-split refactor(cli): split main.rs into focused cli/ modules

main

11 hours ago

docs(changelog): record main.rs split under Internal in Unreleased Per CONTRIBUTING.md the main.rs split is internal-only and doesn't strictly require a changelog entry. Adding one anyway because (a) there's precedent in v1.5.0's Internal section, and (b) a refactor reorganising ~3400 lines of code across seven new modules is meaningful enough that contributors browsing the changelog should be able to see it happened. The entry summarises the module layout, calls out the three function-signature narrowings, and references the Cli flatten refactor (shipped in v1.5.0) as the deliberate precondition. Lands first on this branch; will be on `main` after the PR merges and the cli/ extraction commits land alongside it.

refactor/main-rs-split

11 hours ago

main

12 hours ago

docs(changelog): merge the two ### Changed sections in Unreleased Audit of the Unreleased section against every commit since v1.4.2 turned up a structural bug: two `### Changed` headings in the same release block. They were created independently — one for the `#[non_exhaustive]` annotations (committed during the v1.4.3 backfill via 2a3846b), one for the `--fast` demotion (added later in the same backfill commit). Neither author noticed the duplication. The released changelog would have rendered with two Changed sections under one version header — confusing for readers, ugly on docs site, and a minor regression in changelog hygiene. Merge both bullets under a single Changed heading. Section order in Unreleased is now the conventional Added → Changed → Fixed → Internal → Documentation. No bullet content changed; only the heading topology. Confirmed via audit that every user-visible commit since v1.4.2 has an entry. Internal-only commits (WriteCtx refactor, ci_get extraction, Cli flatten, MSRV CI, proptest harness, etc.) are deliberately skipped per CONTRIBUTING.md's standing rule.

main

13 hours ago

Merge pull request #60 from cmakefmt/dependabot/github_actions/taiki-e/install-action-2.78.2 chore(deps): bump taiki-e/install-action from 2.78.1 to 2.78.2

main

16 hours ago

Latest Branches

0%

refactor(cli): split main.rs into focused cli/ modules#61

11 hours ago

a47ee1d

refactor/main-rs-split

0%

chore(deps): bump taiki-e/install-action from 2.78.1 to 2.78.2#60

1 day ago

c93d5f5

dependabot/github_actions/taiki-e/install-action-2.78.2

0%

chore(deps): bump github/codeql-action from 4.35.4 to 4.35.5#59

2 days ago

407c96b

dependabot/github_actions/github/codeql-action-4.35.5

© 2026 CodSpeed Technology

Home Terms Privacy Docs