docs(changelog): set [1.0.1] tag date to 2026-06-09 (tag-date prep)#16
Merged
Conversation
Tag-date prep slice — replace both <YYYY-MM-DD pending tag> placeholders (top-of-file metadata Date and the [1.0.1] section heading) with the intended tag date 2026-06-09. No other content changes. This mirrors the T0 tag-date prep slice for v1.0.0 (PR #11, set [1.0.0] tag date to 2026-06-09). After this lands, the annotated v1.0.1 tag will be pushed against the resulting tree as a separate gate. Validation: - Diff: CHANGELOG.md only, +2 / -2 (both placeholders flipped). - alire.toml version remains "1.0.1" (from PR #14). - src/version/clara-version.ads remains Patch = 1, Version = "1.0.1". - Root alire.toml still has no [[pins]] (T1 / PR #12 removal preserved). - Direct dependency functional = "^4.0.0" unchanged. - .gitmodules HTTPS for both public helper submodules (PR #13 preserved). - v1.0.0 annotated tag preserved at e3c24f4 -> 8b6ea3b (NOT re-pointed). - v1.0.1 tag still does not exist locally or remotely. - No GitHub Release on clara. - alr publish was not run. Refs: adafmt#42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Tag-date prep slice for clara v1.0.1. Replaces both
<YYYY-MM-DD pending tag>placeholders inCHANGELOG.mdwith the chosen tag date2026-06-09. No other content changes.Mirrors the T0 tag-date prep slice for v1.0.0 (PR #11, which set
[1.0.0]tag date to2026-06-09). After this lands, the annotatedv1.0.1tag will be pushed against the resulting tree as a separate gate.Commit map
79c2e8cdocs(changelog): set [1.0.1] tag date to 2026-06-09 (tag-date prep)CHANGELOG.md(+2 / −2)Diff total: 1 file, +2 / −2.
Exact CHANGELOG date edits
Both placeholders flipped surgically. No other lines in
CHANGELOG.mdtouched.Validation (performed before PR open)
CHANGELOG.mdonlygit diff --check(whitespace)alire.tomlversion remains1.0.1src/version/clara-version.adsremainsPatch = 1, Version = "1.0.1"alire.tomlstill has no[[pins]](T1 / PR #12 removal preserved)functional = "^4.0.0"unchanged.gitmodulesHTTPS-clean for both public helper submodules (PR #13 preserved)v1.0.0tag preserved (e3c24f4→8b6ea3b)v1.0.1tag still does not exist locally or remotelyfatal: ambiguous argument(expected absence)gh release listemptyalr publishwas not runclara-1.0.1.toml404 (state from earlier verification still holds)clara#15(test/config drift) NOT addressed in this PRPosition in the v1.0.1 release sequence
[1.0.0]tag-date prep (PR #11)[[pins]] functionalremoval (PR #12)27177524751v1.0.0tag pushede3c24f4→8b6ea3b)v1.0.0tree.gitmodules).gitmodulesSSH → HTTPS repair (PR #13)ec80afd)dbcbeb0)[1.0.1]tag date set to 2026-06-09 (this PR)v1.0.1tag pushalr publish --skip-submitonv1.0.1treealr publishsubmit to alire-indexv1.0.1What this PR does NOT do
alire.toml/test/alire.toml/clara-version.ads/test/unit/test_version.adbedits (all preserved from PR chore(release): bump version 1.0.0 -> 1.0.1 (first Alire-published release) #14).v1.0.1annotated tag is a separate gate.alr publishrun..gitmoduleschanges (PR fix(gitmodules): switch submodule URLs from SSH to HTTPS for publishability #13 repair preserved).clara#15(test/config tracked-baseline drift) — that's an independent follow-up.astengine,astfmt,adafmt,corpus_ada,hybrid_app_ada,hybrid_lib_ada,tzif_ada, orzoneinfo_ada.clara main branch ruleset state
Push surfaced the
Lock all branchesruleset (id13699088) auto-bypass oncreation, same pattern as PR #10 / #11 / #12 / #13 / #14. Merge will requiregh pr merge --adminwith an audit-trail body when authorized.Follow-ups deliberately deferred
v1.0.1tag push against the tree resulting from this PR.alr publish --skip-submitagainstv1.0.1.alr publishsubmit. Irreversible.gh release create v1.0.1 --verify-tag.Refs: adafmt#42