From 1b75f1cdbd73c03f6cbfcd6d392939b086d87a4c Mon Sep 17 00:00:00 2001 From: Marcin Obel Date: Fri, 19 Jun 2026 16:53:48 +0200 Subject: [PATCH] docs: sync CITATION.cff to v0.1.2 and document the bump in the release flow CITATION.cff still read 0.1.1/2026-06-14 after the v0.1.2 release; update it and add a CITATION.cff bump to the CONTRIBUTING release checklist so it can't drift again. --- CITATION.cff | 4 ++-- CONTRIBUTING.md | 3 ++- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/CITATION.cff b/CITATION.cff index 99656a4..6db5897 100644 --- a/CITATION.cff +++ b/CITATION.cff @@ -8,5 +8,5 @@ authors: repository-code: 'https://github.com/qodeca/8cli' url: 'https://github.com/qodeca/8cli' license: GPL-3.0-only -version: 0.1.1 -date-released: 2026-06-14 +version: 0.1.2 +date-released: 2026-06-19 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 243a0cb..908107a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -91,7 +91,8 @@ Use the GitHub issue templates. For security vulnerabilities, follow Releases publish to npm automatically via **trusted publishing** (OIDC) – do not run `npm publish` by hand for normal releases. The flow: -1. Bump `version` in `package.json` (follow [SemVer](https://semver.org)). +1. Bump `version` in `package.json` (follow [SemVer](https://semver.org)), and update + `version` + `date-released` in `CITATION.cff` to match. 2. Move the relevant `CHANGELOG.md` entries from `[Unreleased]` into the new version section. 3. Commit, then create a matching **signed, annotated** tag (`git tag -s v0.2.0 -m "v0.2.0"`) and a **GitHub Release** (for example `v0.2.0`).