From 4dae7a58b007f9d2adc6289a9d03d38b21cdf315 Mon Sep 17 00:00:00 2001 From: Moritz Mazetti Date: Thu, 30 Jul 2026 15:38:00 +0200 Subject: [PATCH] chore: release 0.1.1 v0.1.0 was tagged but never published: its release run failed in the first job on the git cat-file tag check, fixed in #12. Nothing reached any registry. Re-tagging v0.1.0 would have been tidier, but the Immutable release tags ruleset refused the deletion -- for me too, since it has no bypass actors. That control exists precisely to stop a published version tag being moved, and weakening it to correct a version number in a repository whose whole point is supply-chain rigour would be the wrong trade. So the tag stays, pointing at a commit that was never released, and 0.1.1 becomes the first published version. The changelog records why 0.1.0 does not exist on any registry, so nobody has to reconstruct it from workflow logs later. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01CEdTd43qLEEE5qCsL1A7gW --- CHANGELOG.md | 15 ++++++++++++--- js/package.json | 2 +- pyproject.toml | 2 +- src/matchory_coding_style/__init__.py | 2 +- 4 files changed, 15 insertions(+), 6 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 753a717..d752524 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -22,7 +22,16 @@ even though nothing about the interface moved. Nothing yet. -## [0.1.0] — 2026-07-30 +## [0.1.1] — 2026-07-30 + +First published release. + +`v0.1.0` was tagged but never published. Its release run failed in the first job, because the workflow +used `git cat-file` to check that the tag was annotated and `actions/checkout` materialises a tag ref as +a lightweight local tag inside a runner. The tag itself was correct; the check was not. Since the +repository forbids deleting or moving a `v*` tag — a control that did its job here, refusing even an +administrator — the tag stays, pointing at a commit that was never released, and the first published +version is `0.1.1`. First release. Presets for Pint, PHPStan, Rector, oxlint, oxfmt, ESLint, TypeScript and ruff, plus the canonical `.editorconfig`. @@ -93,5 +102,5 @@ ecosystems, so a malicious version would run in our CI and on developer machines Composer has no artefact provenance mechanism, so the PHP package's integrity rests on repository protection and signed tags instead. -[Unreleased]: https://github.com/matchory/coding-style/compare/v0.1.0...HEAD -[0.1.0]: https://github.com/matchory/coding-style/releases/tag/v0.1.0 +[Unreleased]: https://github.com/matchory/coding-style/compare/v0.1.1...HEAD +[0.1.1]: https://github.com/matchory/coding-style/releases/tag/v0.1.1 diff --git a/js/package.json b/js/package.json index 7a84622..c72bff2 100644 --- a/js/package.json +++ b/js/package.json @@ -1,6 +1,6 @@ { "name": "@matchory/coding-style", - "version": "0.1.0", + "version": "0.1.1", "description": "Shared code style configuration for Matchory projects: oxlint, oxfmt, ESLint and TypeScript presets.", "license": "MIT", "private": false, diff --git a/pyproject.toml b/pyproject.toml index ea8081a..c64f33f 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -12,7 +12,7 @@ [project] name = "matchory-coding-style" -version = "0.1.0" +version = "0.1.1" description = "Shared code style configuration for Matchory projects: ruff presets and the canonical .editorconfig." readme = "README.md" requires-python = ">=3.11" diff --git a/src/matchory_coding_style/__init__.py b/src/matchory_coding_style/__init__.py index 9e39e9c..d9cd88b 100644 --- a/src/matchory_coding_style/__init__.py +++ b/src/matchory_coding_style/__init__.py @@ -7,4 +7,4 @@ __all__ = ["__version__"] -__version__ = "0.1.0" +__version__ = "0.1.1"