You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Traceback (most recent call last):
File "/home/runner/work/_actions/connectbot/actions/d8a1b65644a6eea1ceb35810d342fa64bc8be449/publish/../scripts/publish_release.py", line 267, in <module>
main()
~~~~^^
File "/home/runner/work/_actions/connectbot/actions/d8a1b65644a6eea1ceb35810d342fa64bc8be449/publish/../scripts/publish_release.py", line 209, in main
require_publish_ready(pr_number, pr_data)
~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
File "/home/runner/work/_actions/connectbot/actions/d8a1b65644a6eea1ceb35810d342fa64bc8be449/publish/../scripts/publish_release.py", line 154, in require_publish_ready
raise RuntimeError("Release is not ready:\n\n" + "\n".join(f"- {b}" for b in blockers))
RuntimeError: Release is not ready:
- PR #377 has merge state UNSTABLE. Open the PR's merge section and resolve the remaining branch requirements before retrying.
Next: resolve the blockers above. Submit an Approve review on the release PR and wait for all required checks to pass. Leave the PR open and in draft; do not merge it.
If no release tag was pushed, use Re-run failed jobs on the linked run, or remove and reapply release:publish on this issue. If the tag already exists, check the tag-triggered publishing run before retrying.
Published tag v0.6.4 and advanced main to 0.6.5-SNAPSHOT.
Next: check the repository's Actions tab for the tag-triggered artifact publishing run. This action does not upload artifacts. Once publishing succeeds, close this release issue.
Activity
connectbot-release-manager commentedon Oct 25, 2026
Prepared v0.6.4 for
mainin PR #377.Next steps:
release:publishto this issue.Leave the PR open and in draft. Do not merge it or mark it ready for review. The publish action will tag the release and advance the target branch.
connectbot-release-manager commentedon Oct 25, 2026
Publish release failed.
Next: resolve the blockers above. Submit an Approve review on the release PR and wait for all required checks to pass. Leave the PR open and in draft; do not merge it.
If no release tag was pushed, use Re-run failed jobs on the linked run, or remove and reapply
release:publishon this issue. If the tag already exists, check the tag-triggered publishing run before retrying.Run: https://github.com/connectbot/cbssh/actions/runs/40170947261
connectbot-release-manager commentedon Oct 25, 2026
Published tag
v0.6.4and advancedmainto0.6.5-SNAPSHOT.Next: check the repository's Actions tab for the tag-triggered artifact publishing run. This action does not upload artifacts. Once publishing succeeds, close this release issue.