build(release): track single root product version in release-please

Veect is a hosted SaaS deploying continuously (ADR-027), so release-please
now tracks only the root package with plain v* tags. Drops the five
packages/* entries ahead of story 03's feature deletions so ADR-021's
commit -> release automation keeps working through them.

include-component-in-tag is set to false rather than removed: the
upstream default is true and the node strategy derives a component from
package.json, so literal key removal would keep component-prefixed tags
(template-vertical-v*) instead of the wanted plain v* tags.

Pre-1.0 bump policy (bump-patch-for-minor-pre-major) and changelog
sections are retained. The release workflow's SBOM steps already use the
tag-format-agnostic tag_name output; only its header comment needed
updating. Per-feature CHANGELOG.md files stay on disk untracked by
release-please until story 03 deletes them with their packages.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016j8z4VHjedXDTjEDNg7qHK
This commit is contained in:
2026-07-12 15:04:23 +02:00
parent 5a26eeed9b
commit 8224247009
3 changed files with 10 additions and 41 deletions

View File

@@ -2,20 +2,20 @@
#
# How it works:
# 1. On every push to main, release-please scans conventional commits since
# the last release tag for each tracked package.
# the last release tag.
# 2. It opens (or updates) a single rolling "release PR" containing:
# - version bumps in each affected package.json
# - the root package.json version bump
# - new CHANGELOG.md entries grouped by section (Features / Bug Fixes
# / Performance / Refactoring / Documentation / Reverts)
# - updated .release-please-manifest.json
# 3. Merging that PR triggers tag creation (`template-vN.N.N`, `auth-vN.N.N`,
# etc.) and GitHub release notes.
# 3. Merging that PR triggers tag creation (`vN.N.N`) and GitHub release
# notes.
#
# Hybrid versioning (ADR-021): root template versions independently from the
# 5 feature packages. Tags use the per-package component prefix so they don't
# collide (e.g. `template-v0.2.0` vs `auth-v0.1.1`).
# Single product version (ADR-027 supersedes ADR-021's hybrid scheme): Veect
# is a hosted SaaS deploying continuously, so only the root package is
# tracked and tags are plain `v*` (`include-component-in-tag: false`).
#
# Tracked packages, manifest baseline, and changelog sections live in
# Tracked package, manifest baseline, and changelog sections live in
# `release-please-config.json` + `.release-please-manifest.json`.
name: Release Please