Skip to content

docs: sync CITATION.cff to v0.1.2 #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
marcinobel merged 1 commit into from
Jun 19, 2026
Merged

docs: sync CITATION.cff to v0.1.2 #14

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CITATION.cff
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
3 changes: 2 additions & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`).
Expand Down
Loading