Skip to content

chore(release): 0.1.141-unstable.20260826103323 - #750

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

chore(release): 0.1.141-unstable.20260826103323#750
github-actions[bot] wants to merge 1 commit into
developmentfrom
release/v0.1.141-unstable.20260826103323

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Version bump for 0.1.141-unstable.20260826103323, opened by the release workflow.

The tag v0.1.141-unstable.20260826103323 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 26, 2026 10:35
@rubenvdlinde

Copy link
Copy Markdown
Contributor

Closing as obsolete. This is not a backwards bump — it proposes 0.1.141-unstable.20260826103323, newer than development's 0.1.141-unstable.20260826085431. It conflicts because development advanced past the point this branch was cut, and both sides edit the same <version> line.

The release workflow regenerates a current bump on its next run. Context in ConductionNL/.github#562: gate 1 ([skip ci] suppressing the required check) is fixed in #578; gate 2 (runs held at action_required by an org-level approval policy) remains open and is cleared by hand during sweeps.

auto-merge was automatically disabled August 26, 2026 13:14

Pull request was closed

@rubenvdlinde
rubenvdlinde deleted the release/v0.1.141-unstable.20260826103323 branch August 26, 2026 13:14
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