Skip to content

fix: remove unintended stable-tag protection requirement - #1146

Closed
MichalCz wants to merge 11 commits into
mainfrom
release/2.3.1
Closed

MichalCz wants to merge 11 commits into
mainfrom
release/2.3.1

Conversation

@MichalCz

Copy link
Copy Markdown
Member

This change allows ordinary stable-tag pushes to pass publication admission when GitHub reports the tag ref as unprotected. Recovery dispatches remain restricted to protected main. Existing tag-to-current-main SHA, release-bundle identity/checksum, and production approval controls remain unchanged.\n\nValidation: 29 focused tests passed via the supported runner; workflow policy and YAML checks passed. No tags or releases were changed, and this PR does not publish packages.

github-actions Bot and others added 11 commits October 13, 2026 12:31
* chore(deps): update compatible workspace dependencies

* chore(deps): preserve caret ranges for Docker typings
Co-authored-by: OpenCode <opencode@localhost>
* chore(deps): apply safe security updates and compatible major upgrades

* test: align documentation invariant with adopted guide

* test(cli): isolate configuration paths per AVA worker

* test: remove out-of-scope dependency update tests

* test: remove out-of-scope CLI isolation setup

* fix(cli): honor SCRAMJET_HOME and isolate test worker state
@MichalCz MichalCz closed this Oct 14, 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