Skip to content

chore(release): 0.1.142-unstable.20260827172941 - #772

Closed
github-actions[bot] wants to merge 1 commit into
developmentfrom
release/v0.1.142-unstable.20260827172941
Closed

chore(release): 0.1.142-unstable.20260827172941#772
github-actions[bot] wants to merge 1 commit into
developmentfrom
release/v0.1.142-unstable.20260827172941

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Version bump for 0.1.142-unstable.20260827172941, opened by the release workflow.

The tag v0.1.142-unstable.20260827172941 already names this commit, so the released
package and its label agree. Merging this brings development up
to the released version.

Raised as a pull request rather than pushed directly because
development requires one; a direct push is rejected with GH013
and takes the release down with it.

@github-actions
github-actions Bot enabled auto-merge (squash) August 27, 2026 17:31
@github-actions

Copy link
Copy Markdown
Contributor Author

Quality Report — ConductionNL/stackiq @ 87d7aa1

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-manifest
check-vue-demi
test-l10n
format
check-schema-l10n
check-l10n-js
composer ✅ 130/130
npm ✅ 721/721
app:check-code ⏭️
info.xml
REUSE
PHPUnit
Newman ⏭️
Playwright
Hydra gates

Quality workflow — 2026-08-27 20:57 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Closing as superseded.

This pull request was opened by the release workflow to bring development up to a tagged version. It could never merge: the org-level Development Branch Protection ruleset requires 1 approving review on development, and nothing reviews a bot PR — so auto-merge stayed armed with every check green and the PR sat open. Each release added another; the backlog reached 49 across 9 repos, and on some repos they began conflicting with each other because they all rewrite the same <version> line.

The version this PR carries is already published under its tag. development will catch up on the next release once the loop is fixed (adding the release bot as a ruleset bypass actor), so nothing is lost by closing this.

auto-merge was automatically disabled August 27, 2026 21:03

Pull request was closed

@rubenvdlinde
rubenvdlinde deleted the release/v0.1.142-unstable.20260827172941 branch August 27, 2026 21:03
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