Skip to content

release: workflow runner v0.4.56 - #46

Merged
animus-launchapp-gitprovider[bot] merged 1 commit into
mainfrom
release/v0.4.56
Jul 29, 2026
Merged

release: workflow runner v0.4.56#46
animus-launchapp-gitprovider[bot] merged 1 commit into
mainfrom
release/v0.4.56

Conversation

@Shooksie

Copy link
Copy Markdown
Contributor

Coordinated stability release for merged PR #45 and Animus core PR #354.\n\n- bumps the runner package and lockfile to v0.4.56\n- includes fail-closed durable publication holds, exact-handle reattachment, and exactly-once publication cleanup\n- runner CI and 314 tests are green; coordinated external cancellation is supplied by Animus CLI rc.33\n\nMerge only after checks are green. Tag v0.4.56 from the merge commit, then require all release assets before assembling Portal runtime-v12.

@animus-launchapp-gitprovider animus-launchapp-gitprovider Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT: APPROVE

No findings. At exact head 3a955f831ad0b3225ebbb3585efebbbbe9bc23f7, the diff is a minimal mechanical release bump: Cargo.toml and the root package entry in Cargo.lock both move only from 0.4.55 to 0.4.56. No implementation files are changed or dropped, and the Rust quality gate completed successfully.

What is good: the package manifest and lockfile remain synchronized, the PR is tightly scoped to the requested release metadata, and CI is green.

@animus-launchapp-gitprovider
animus-launchapp-gitprovider Bot merged commit 2eb468f into main Jul 29, 2026
1 check passed

@animus-launchapp-gitprovider animus-launchapp-gitprovider Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT: APPROVE

The release change is correct, complete, and minimal: Cargo.toml and the root package entry in Cargo.lock are both bumped consistently from 0.4.55 to 0.4.56, with no unrelated changes. The Rust quality gate completed successfully for head 3a955f831ad0b3225ebbb3585efebbbbe9bc23f7.

What is good: the package manifest and lockfile remain synchronized, the diff is tightly scoped to the release, and the PR body clearly documents the coordinated release context and post-merge tagging requirements.

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