Skip to content

chore(release): 0.3.2-unstable.20260908134238 - #666

Closed
rubenvdlinde wants to merge 1 commit into
developmentfrom
release/v0.3.2-unstable.20260908134238
Closed

chore(release): 0.3.2-unstable.20260908134238#666
rubenvdlinde wants to merge 1 commit into
developmentfrom
release/v0.3.2-unstable.20260908134238

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Version bump for 0.3.2-unstable.20260908134238, opened by the release workflow.

The tag v0.3.2-unstable.20260908134238 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.

@rubenvdlinde
rubenvdlinde enabled auto-merge (squash) September 8, 2026 13:44
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/keepiq @ 843c15f

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-manifest
test-l10n
format
check-l10n-js
check-schema-l10n
composer ✅ 111/111
npm ✅ 543/543
app:check-code ⏭️
info.xml
REUSE
PHPUnit
Newman
Playwright ⏭️ deferred — runs on the promotion into beta/main, not on a pull request into development
Hydra gates

Quality workflow — 2026-09-08 13:50 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde

Copy link
Copy Markdown
Contributor Author

Closing this version bump rather than merging it.

The release workflow opens a bump PR on every push to development, so merging one is itself a push and opens the next. The queue cannot reach zero that way, and the workflow supersedes its own previous bump branch, so nothing is lost by closing.

A bump gets merged when we actually want that version on development, not to clear the list.

auto-merge was automatically disabled September 9, 2026 05:56

Pull request was closed

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