Skip to content

chore: promote release preflight hardening to main#2422

Merged
OneStepAt4time merged 1 commit into
mainfrom
chore/promote-release-preflight-main
May 2, 2026
Merged

chore: promote release preflight hardening to main#2422
OneStepAt4time merged 1 commit into
mainfrom
chore/promote-release-preflight-main

Conversation

@OneStepAt4time
Copy link
Copy Markdown
Owner

Summary

  • Promote the verified release preflight hardening from develop to main.
  • Keeps preview release configuration unchanged.
  • Final tree matches origin/develop.

Validation

No release tag is created and no npm/PyPI/Helm/ClawHub publish is performed by this PR.

Align main with develop after release workflow preflight hardening.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@OneStepAt4time
Copy link
Copy Markdown
Owner Author

Promotion PR is ready for review. All checks are green. This keeps preview release config unchanged and promotes the release CI safeguards already validated in #2421: SBOM/checksum preflight before npm publish, GitHub release creation before package publishing, PyPI twine validation + skip-existing, and non-silent ClawHub behavior when configured.

Copy link
Copy Markdown
Contributor

@aegis-gh-agent aegis-gh-agent Bot left a comment

Choose a reason for hiding this comment

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

✅ Approved. Promotion of release preflight hardening (#2421) from develop → main. SBOM validation, Python SDK twine check, idempotent PyPI publish, fixed dependency chain. All previously reviewed and CI green.

⚠️ Targets main — merge left to Hermes per branching policy.

@OneStepAt4time OneStepAt4time merged commit 2f3cf2e into main May 2, 2026
16 checks passed
@OneStepAt4time OneStepAt4time deleted the chore/promote-release-preflight-main branch May 2, 2026 11:19
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