Second layer of the release fix (follows the revived #171 fix in the previous commit; PR #185 was superseded by this branch).
Problem
With HEAD:master + token auth, the auto-bump push now reaches Gitea but is rejected: "Not allowed to push to protected branch master" (run 792). Branch protection forbids direct pushes to master by design (enable_push=false, block_admin_merge_override=true) — the auto-bump must not bypass the same gate every feature PR passes through.
Fix
The auto-bump step now performs the governed flow itself, via API:
create chore/auto-bump-X.Y.Z+1 branch from master;
commit the five version-surface edits via the contents API (graceful skip of absent surfaces);
open the bump PR;
wait for the same protected check (CI Pipeline / required-checks (pull_request)) to go green (15-min ceiling);
merge via the pulls API (branch protection respected);
export the bumped version for the release step.
Release creation step is unchanged. No branch-protection semantics weakened; the bump now travels the identical gate as feature work.
Second layer of the release fix (follows the revived #171 fix in the previous commit; PR #185 was superseded by this branch).
## Problem
With HEAD:master + token auth, the auto-bump push now reaches Gitea but is rejected: "Not allowed to push to protected branch master" (run 792). Branch protection forbids direct pushes to master by design (enable_push=false, block_admin_merge_override=true) — the auto-bump must not bypass the same gate every feature PR passes through.
## Fix
The auto-bump step now performs the governed flow itself, via API:
1. create `chore/auto-bump-X.Y.Z+1` branch from master;
2. commit the five version-surface edits via the contents API (graceful skip of absent surfaces);
3. open the bump PR;
4. wait for the same protected check (`CI Pipeline / required-checks (pull_request)`) to go green (15-min ceiling);
5. merge via the pulls API (branch protection respected);
6. export the bumped version for the release step.
Release creation step is unchanged. No branch-protection semantics weakened; the bump now travels the identical gate as feature work.
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.
Second layer of the release fix (follows the revived #171 fix in the previous commit; PR #185 was superseded by this branch).
Problem
With HEAD:master + token auth, the auto-bump push now reaches Gitea but is rejected: "Not allowed to push to protected branch master" (run 792). Branch protection forbids direct pushes to master by design (enable_push=false, block_admin_merge_override=true) — the auto-bump must not bypass the same gate every feature PR passes through.
Fix
The auto-bump step now performs the governed flow itself, via API:
chore/auto-bump-X.Y.Z+1branch from master;CI Pipeline / required-checks (pull_request)) to go green (15-min ceiling);Release creation step is unchanged. No branch-protection semantics weakened; the bump now travels the identical gate as feature work.