Skip to content

chore(release): prepare 0.14.4 - #71

Merged
div0-space merged 3 commits into
mainfrom
release/v0.14.4
Aug 23, 2026
Merged

chore(release): prepare 0.14.4#71
div0-space merged 3 commits into
mainfrom
release/v0.14.4

Conversation

@div0-space

@div0-space div0-space commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • synchronize Cargo, npm, editor, installer, docs, and bundle surfaces at Loctree 0.14.4
  • select AICX 0.12.5 as the canonical combined-bundle input
  • preserve immutable failed-tag provenance and record the corrective Windows release evidence

Why

The v0.14.3 tag proved four targets but exposed Windows contract failures. PR #70 repaired the five-target release workflow. AICX 0.12.5 is now published, checksum/signature verified, npm published, and cold-installed on hosted macOS/Linux/Windows plus the real SSH Windows host. This corrective version publishes those already-merged fixes without moving or rewriting v0.14.3.

Verification

  • make version-assert
  • make test
  • make preflight
  • make semgrep
  • node distribution/npm/publish-if-missing.test.mjs
  • bash distribution/tests/windows_bundle_test.sh
  • actionlint .github/workflows/release-bundles.yml
  • branch rehearsal 32672964365: exact head 3e6e090152c0db904048b6b5d2673990a5ed5112; macOS arm64/x64, Linux GNU/musl, and Windows MSVC all passed; branch-only publish correctly skipped
  • Windows rehearsal smoke: Loctree 0.14.4+g3e6e0901, AICX 0.12.5+gced57997, all six binaries and committed-fixture scan passed
  • Debian 12 musl rehearsal smoke: static binary confirmed and committed one-file Git fixture scanned successfully without Git installed in the container
  • $vc-deprivatize full scan compared against the established clean-HEAD baseline: unchanged 1337-finding profile (627 critical, 177 high, 533 medium), with the same inherited 560 unambiguous findings; this release cut adds zero findings and does not claim the historical repository is clean

The tag will be created only from exact merged main. The immutable tag workflow must repeat all five platform proofs before npm publication.

Authored-By: codex agents@vetcoders.io

div0-space and others added 3 commits August 23, 2026 22:37
Synchronize every shipped Loctree surface at 0.14.4 and select the corrective AICX 0.12.4 assets for combined bundles.

Record the five-platform Windows repair evidence and keep the failed v0.14.3 tag immutable.

Authored-By: codex <agents@vetcoders.io>
Advance the Loctree 0.14.4 combined-bundle contract from the failed immutable AICX 0.12.4 tag to the verified 0.12.5 release. Keep workflow, Make, docs, tests, and the research ledger aligned with the public Windows, npm, and real-host evidence.

Authored-By: codex <agents@vetcoders.io>

session_id: 01a02e76-59c6-70b1-b8c0-a032a6a28796

timestamp: 2026_0824_0112_CEST

runtime: vibecrafted
@div0-space
div0-space merged commit 3e9eb0a into main Aug 23, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant