v1.0.2

Summary

Release meta

Released on: 2026-08-14
Released by: ggrossetie
Published by: GitHub

Logs: full diff

Changelog

Infrastructure

• Make the GitHub repository public; npm provenance attestations require a public source repository, and publishing with --provenance was failing against the previously private repo
• Bump actions/checkout and actions/setup-node to v7, and test against Node.js 20/22/24 instead of 18/20/22

v1.0.1

Summary

Release meta

Released on: 2026-08-14
Released by: github-actions[bot]
Published by: GitHub

Logs: full diff

Changelog

Changed

• Publish under the @bestikk/changelog npm scope instead of the unscoped bestikk-changelog name; the CLI command is still bestikk-changelog

Infrastructure

• Convert README.adoc to README.md at publish time (via downdoc’s --prepublish/--postpublishlifecycle scripts), since npmjs.com doesn’t render AsciiDoc;README.adoc` remains the source of truth on GitHub

v1.0.0

Summary

Initial release.

Release meta

Released on: 2026-08-07
Released by: Guillaume Grossetie
Published by: GitHub

Changelog

Added

• release and notes library functions and CLI commands to manage a Keep a Changelog (https://keepachangelog.com) style CHANGELOG.adoc: roll the == Unreleased section into a dated == v<version> (<date>) section, and extract a release section as Markdown release notes (via downdoc) suitable for a GitHub release
• Support a native Markdown changelog (e.g. CHANGELOG.md) as an alternative to AsciiDoc, selected via the format option (adoc/markdown) or auto-detected by the CLI from the --file extension
• Make downdoc an optional dependency, loaded lazily only when processing the adoc format, so a Markdown-only changelog doesn’t require it
• Support configurable "Unreleased"/release heading syntax via the style option (keepachangelog, title-paren, title-paren-suffix, or a custom style object), covering variations such as asciidoctor-emoji’s and asciidoctor-vscode’s changelogs.
  The adoc format shares the same styles, just with the AsciiDoc heading marker instead of Markdown’s — both are a "level 2" heading in their respective syntax

Infrastructure

• Lint and format the codebase with Biome (npm run lint, npm run lint:fix, npm run format)
• Add a Test GitHub Actions workflow running lint and the test suite on Node 18/20/22 for every push and pull request
• Add a Release GitHub Actions workflow (manually dispatched with a version) that bumps the package version, rolls the changelog, tags, publishes to npm, and creates the GitHub release using this project’s own CLI