ci(pypi): workflow_dispatch fuer Guard-Beweis-Lauf - #38
Conversation
Ohne dispatch konnte der 06-06-Guard erst beim naechsten Release einen gruenen/skipped Run erzeugen - der Estate-Workflow-Scan haette bis dahin den historischen 05-28-Fail gemeldet. Job skipt weiterhin ohne PYPI_PUBLISH_ENABLED=true. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bf6dcc8518
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| on: | ||
| release: | ||
| types: [published] | ||
| workflow_dispatch: # manueller Guard-Beweis-Lauf (Job skipt ohne PYPI_PUBLISH_ENABLED) |
There was a problem hiding this comment.
Once PYPI_PUBLISH_ENABLED is set to true as the workflow comments instruct, a manual dispatch will satisfy the existing job condition, receive id-token: write, check out the dispatched ref, and publish it to PyPI without a published GitHub release. This permanently turns the intended guard-proof trigger into a release-process bypass; include an event-type check in the publishing condition so workflow_dispatch runs remain skipped even after publishing is enabled.
Useful? React with 👍 / 👎.
1 participant
1-Zeiler-Folge zu #37: dispatch-Trigger, damit der Guard sofort einen skipped-Run erzeugen kann (Estate-Scan-Hygiene). Job bleibt ohne PYPI_PUBLISH_ENABLED=true geskippt.