.gitea/workflows/release.yml: started by hand with a version and dry_run (default true). It runs tools/release.py with the token of its own run (ADR-0007); TOKEN_FOR_GITEA_RELEASE overrides it when set.
tools/release.py: refuses unless the commit is the tip of main, its Validate workflows / validate (push) status is success, the changelog has an entry for the version and the tag does not exist; then creates the release page from the changelog entry (which creates the tag) and moves the major tag when the version is the highest of its major.
tests/test_release.py: 19 offline tests, including the two acceptance criteria of US-001.11 and US-001.12.
Release-process guide, changelog (Unreleased) and README row updated; Capabilities wiki page regenerated and its da/ms translations updated.
The workflow is for this repository only (a workflow_dispatch, not a workflow_call). The use case is UC-006; no new use case was needed.
Not yet verified: that the job token may create the tag and move the major tag. The first real run (the dry run of 1.0.0) is the check; ADR-0007 names the fallback.
Adds the release workflow (MIL-004 task 5).
- `.gitea/workflows/release.yml`: started by hand with a version and `dry_run` (default `true`). It runs `tools/release.py` with the token of its own run (ADR-0007); `TOKEN_FOR_GITEA_RELEASE` overrides it when set.
- `tools/release.py`: refuses unless the commit is the tip of `main`, its `Validate workflows / validate (push)` status is success, the changelog has an entry for the version and the tag does not exist; then creates the release page from the changelog entry (which creates the tag) and moves the major tag when the version is the highest of its major.
- `tests/test_release.py`: 19 offline tests, including the two acceptance criteria of US-001.11 and US-001.12.
- Release-process guide, changelog (Unreleased) and README row updated; Capabilities wiki page regenerated and its da/ms translations updated.
The workflow is for this repository only (a `workflow_dispatch`, not a `workflow_call`). The use case is UC-006; no new use case was needed.
Not yet verified: that the job token may create the tag and move the major tag. The first real run (the dry run of `1.0.0`) is the check; ADR-0007 names the fallback.
Closes #24
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds the release workflow (MIL-004 task 5).
.gitea/workflows/release.yml: started by hand with a version anddry_run(defaulttrue). It runstools/release.pywith the token of its own run (ADR-0007);TOKEN_FOR_GITEA_RELEASEoverrides it when set.tools/release.py: refuses unless the commit is the tip ofmain, itsValidate workflows / validate (push)status is success, the changelog has an entry for the version and the tag does not exist; then creates the release page from the changelog entry (which creates the tag) and moves the major tag when the version is the highest of its major.tests/test_release.py: 19 offline tests, including the two acceptance criteria of US-001.11 and US-001.12.The workflow is for this repository only (a
workflow_dispatch, not aworkflow_call). The use case is UC-006; no new use case was needed.Not yet verified: that the job token may create the tag and move the major tag. The first real run (the dry run of
1.0.0) is the check; ADR-0007 names the fallback.Closes #24