Skip to content

docs: v2.1.4 release notes, changelog backfill and README restructure - #121

Merged
Shinrai merged 4 commits into
nextfrom
docs/v2.1.4-release-notes
Oct 4, 2026
Merged

Shinrai merged 4 commits into
nextfrom
docs/v2.1.4-release-notes

Conversation

@cldmv-bot

@cldmv-bot cldmv-bot Bot commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

🚀 What's Changed

💥 Breaking Changes

No breaking changes

✨ Features

No new features

🐛 Bug Fixes

No bug fixes

📦 Dependencies

No dependency updates

🔧 Other Changes

👥 Contributors

@cldmv-bot cldmv-bot Bot added ! docs → next v4 flow: docs contributor PR targeting the next integration branch type: documentation Relates to docs, README updates, guides, or inline code comments labels Oct 3, 2026
…2.1.2

Every release before v2.0.0, and the v2.1.1 and v2.1.2 patches, shipped
without a per-version changelog file. Each file is written from the diff
against the previous release, notes versions that were never published
to npm, and documents the behaviour changes that shipped in minor or
patch releases (v1.3.0 discovery defaults, the v1.3.2 and v1.3.12
engines floors, v1.3.9 preserving @last modified by). v2.1.3 now links
the v2.1.1 and v2.1.2 changelog files instead of their GitHub Releases.
Adds docs/changelog/v2/v2.1.4.md for the pending release (#117: the
CommonJS entry fails clearly on Node.js without require(esm)), promotes
v2.1.4 to the README What's New Latest block, and links every Recent
Releases entry to its changelog file.

The README follows the CLDMV layout: intro and tagline, badges, What's
New, Key Features, Installation with Node.js requirements, Quick Start,
then the existing CLI, API and configuration reference unchanged,
followed by Documentation, Contributing, Links and License.
The non-JS file, repeatable --input and dependency-folder fixes land in
the same release as #117. Describe each fix, the reported skips, and the
behaviour changes an existing setup could notice.
@Shinrai
Shinrai force-pushed the docs/v2.1.4-release-notes branch from c412a19 to 13c8859 Compare October 4, 2026 00:43
@cldmv-bot cldmv-bot Bot changed the title docs: add the v2.1.4 changelog and restructure the README fix: never write a comment into files that cannot carry one; force-only Markdown headers Oct 4, 2026
@cldmv-bot

cldmv-bot Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor Author

Auto-normalized PR title: rewrote PR title to match the highest-priority commit type (fix).

  • Before: docs: add the v2.1.4 changelog and restructure the README
  • After: fix: never write a comment into files that cannot carry one; force-only Markdown headers

If this isn't what you want, edit the title — the normalizer won't re-fire as long as the title stays conventional.

@cldmv-bot cldmv-bot Bot added area: core Touches core library / runtime source code area: tests Touches test files, fixtures, or test infrastructure labels Oct 4, 2026
@Shinrai Shinrai changed the title fix: never write a comment into files that cannot carry one; force-only Markdown headers docs: v2.1.4 release notes, changelog backfill and README restructure Oct 4, 2026
Shinrai
Shinrai previously approved these changes Oct 4, 2026
@cldmv-bot
cldmv-bot Bot dismissed Shinrai’s stale review October 4, 2026 01:25

The merge-base changed after approval.

@Shinrai
Shinrai enabled auto-merge October 4, 2026 01:25
@Shinrai
Shinrai merged commit 7e526f5 into next Oct 4, 2026
24 checks passed
@cldmv-bot
cldmv-bot Bot deleted the docs/v2.1.4-release-notes branch October 4, 2026 01:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: core Touches core library / runtime source code area: tests Touches test files, fixtures, or test infrastructure ! docs → next v4 flow: docs contributor PR targeting the next integration branch type: documentation Relates to docs, README updates, guides, or inline code comments

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant