chore(release): v0.7.0 #105

Merged

alex merged 1 commit from release-prep/rolling into main 2026-06-26 14:18:29 +02:00

Conversation 0 Commits 1 Files changed 4 +25 -24

release-bot commented 2026-06-26 13:55:48 +02:00

Member

Copy link

Added

ADR-0006 decided: option (c) — don't integrate RNA as a backend (closes #98, resolves the deferred decision from 2026-06-25).

The existing internal lib helpers (lib/conventional-commits.sh, lib/fragments.sh, lib/changelog.sh) remain the substrate. (B1) fragment frontmatter summary: (shipped v0.5.0 via #77) is confirmed as the formal answer to the operator's original "RNA-for-notes-only" lean.

Empirical rationale:

• Source-of-truth mismatch: RNA reads merged PR titles; toolkit reads changelog.d/*.md fragments. Fundamental architectural disagreement.
• Output target mismatch: RNA writes to file/milestone/PR-description; toolkit writes Release Objects directly. Two integration points needed for (a3); the second is already our substrate.
• Convention conflict: RNA defaults to bug: not fix: — would require per-consumer --categorize shim or ecosystem-wide convention shift.
• Bump-decision is OUR substrate: RNA's --categorize emits category labels, not version-bump levels. release-decide.sh isn't replaceable.
• Missing primitives: no Docker image yet (RNA #62), no Release Object output, no CHANGELOG composition.
• Carry-forward-catch lens: 0 of 10 arc-convergence catches (v0.4.0 → v0.6.2) would have been prevented by RNA. The substrate-grounding architectural-arc converged on our internal libs.
• (B1) empirically absorbed the load-bearing need: 4 cuts shipped via (B1) without operator surfacing missing-(a3) pain.

Triggers for re-evaluation documented in ADR-0006 §Decision resolution: RNA gaining Release Object output as first-class backend; RNA gaining a stable Docker image; consumer-side demand for edit-preservation; Forgejo introducing Apps/installation-token primitive.

Does NOT preclude consumers from running RNA in parallel for their own release-notes target (milestone or PR description). The two tools fill different lifecycle stages and can coexist.

### Added **ADR-0006 decided**: option **(c) — don't integrate RNA as a backend** (closes [#98](https://git.frankenbit.de/frankenbit/release-toolkit/issues/98), resolves the deferred decision from 2026-06-25). The existing internal lib helpers (`lib/conventional-commits.sh`, `lib/fragments.sh`, `lib/changelog.sh`) remain the substrate. (B1) fragment frontmatter `summary:` (shipped v0.5.0 via [#77](https://git.frankenbit.de/frankenbit/release-toolkit/issues/77)) is confirmed as the formal answer to the operator's original "RNA-for-notes-only" lean. **Empirical rationale**: - **Source-of-truth mismatch**: RNA reads merged PR titles; toolkit reads `changelog.d/*.md` fragments. Fundamental architectural disagreement. - **Output target mismatch**: RNA writes to file/milestone/PR-description; toolkit writes Release Objects directly. Two integration points needed for (a3); the second is already our substrate. - **Convention conflict**: RNA defaults to `bug:` not `fix:` — would require per-consumer `--categorize` shim or ecosystem-wide convention shift. - **Bump-decision is OUR substrate**: RNA's `--categorize` emits category labels, not version-bump levels. `release-decide.sh` isn't replaceable. - **Missing primitives**: no Docker image yet ([RNA #62](https://code.forgejo.org/forgejo/release-notes-assistant/issues/62)), no Release Object output, no CHANGELOG composition. - **Carry-forward-catch lens**: 0 of 10 arc-convergence catches (v0.4.0 → v0.6.2) would have been prevented by RNA. The substrate-grounding architectural-arc converged on our internal libs. - **(B1) empirically absorbed the load-bearing need**: 4 cuts shipped via (B1) without operator surfacing missing-(a3) pain. **Triggers for re-evaluation** documented in ADR-0006 §Decision resolution: RNA gaining Release Object output as first-class backend; RNA gaining a stable Docker image; consumer-side demand for edit-preservation; Forgejo introducing Apps/installation-token primitive. Does NOT preclude consumers from running RNA in parallel for their own release-notes target (milestone or PR description). The two tools fill different lifecycle stages and can coexist.

release-bot added 1 commit 2026-06-26 13:55:48 +02:00

chore(release): prepare v0.7.0 ... a8dabb13c4

Generated by release-toolkit release-prep.sh.

Tracker: frankenbit/release-toolkit#1

alex merged commit a8dabb13c4 into main 2026-06-26 14:18:29 +02:00

alex deleted branch release-prep/rolling 2026-06-26 14:18:29 +02:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

bump

major

Override the cut bump to MAJOR (release-toolkit#107)

  

bump

minor

Override the cut bump to MINOR (release-toolkit#107)

  

bump

patch

Override the cut bump to PATCH (release-toolkit#107)

  

kind/bug

Something is broken

  

kind/chore

Maintenance, tooling, refactor

  

kind/docs

Documentation work

  

kind/feature

New feature or capability

  

priority/critical

Critical: must be addressed immediately

  

priority/high

Important, should be addressed soon

  

priority/low

Low priority, address when convenient

  

priority/medium

Normal priority

  

size/L

Large: significant feature, ~6-16h

  

size/M

Medium: moderate feature, ~2-6h

  

size/S

Small: simple change, ~1-2h

  

size/XL

Extra large: major feature or refactor, 16h+

No labels

bump

major

bump

minor

bump

patch

kind/bug

kind/chore

kind/docs

kind/feature

priority/critical

priority/high

priority/low

priority/medium

size/L

size/M

size/S

size/XL

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

frankenbit/release-toolkit!105

No description provided.