Skip to content

prototype: explore read-only release planning - #77

Closed
vitormattos wants to merge 6 commits into
mainfrom
feat/release-train-plan
Closed

vitormattos wants to merge 6 commits into
mainfrom
feat/release-train-plan

Conversation

@vitormattos

@vitormattos vitormattos commented Sep 21, 2026 •

Copy link
Copy Markdown
Member

Important

Prototype only — do not merge as the production implementation.

This PR was created to explore the read-only planning contract. The production architecture is now defined by #70 and #78 and is implemented as the PHP CLI/PHAR in LibreCodeCoop/release-tool, with github-workflows providing thin orchestration. #71 remains open until that production implementation satisfies its current contract.

Prototype scope

This PR explored:

  • a read-only release planner;
  • composite-action wrapping;
  • branch/version discovery;
  • immutable planning output;
  • unit-testable Python logic.

Its behavior may be reused or rewritten, but this branch/PR is not the source of truth.

Superseding contracts

Follow:

The old multi-stable assumptions and simplified patch-only behavior in this prototype must not be carried forward unless they match those issues.

Disposition

Keep this PR only as disposable reference material while useful behavior/tests are extracted into the PHP production implementation. Do not merge it. Close/delete it once the relevant production contracts have equivalent or better coverage.

@vitormattos vitormattos changed the title feat: add read-only release train planning prototype: explore read-only release planning Sep 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant