-
v1.1.0 Stable
released this
2026-09-05 14:37:49 +00:00 | 56 commits to main since this releaseAdded
undated-entryandundated-release, a pair the repository's tags decide
between where the newest entry names a version and carries no date. No tag
names that version yet, and the entry is open: a release still accumulating on
a branch of its own, which names its version before its date is known.
undated-entryreports it, defaulting toerrorbecause an entry with no
date is illegal under Keep a Changelog, and a branch accumulating a release
is the one invocation that switches it off inoff:, the way a trunk
invocation switchesprerelease-entryon. A tag already names that version,
and the release shipped and nobody dated it:undated-releasereports that,
also aterror, and switching the other check off does not silence it.
Fifteen checks.- The two are separate because one setting cannot serve both. A stabilization
branch has to admit its open entry on every run, and a release that reached a
tag with no date is a defect on exactly that workflow, so a single check would
be switched off for the whole of the window in which the defect occurs. The
same tag question answers both, and it is the onealready-taggedreports, so
the check and the output cannot disagree about which case a run is in. - Where the tag history cannot be read, the answer is unknowable and the entry
is reported as open.no-git-tagsalready names that cause, and accusing a
repository of shipping an undated release on the strength of tags nobody could
read is the more expensive of the two mistakes.
Changed
heading-formaccepts## [1.2.3]with no date on the newest versioned entry
only, which is the entry the two checks above then answer for. Every entry
below it has shipped and carries a date, so one missing there still fires
heading-form.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads