On v1.1.0 the Chocolatey push failed with HTTP 403 because chocolatey.org still held 1.0.1 in moderation (one version per package in the queue), and the manifests PR, which runs after the push, never opened (#123 was made by hand). The packages job now opens the manifests PR right after updating the manifests, then packs and pushes to Chocolatey; a failed push still fails the job so it is re-run when the queue clears. RELEASING.md documents the behaviour.
On v1.1.0 the Chocolatey push failed with HTTP 403 because chocolatey.org still held 1.0.1 in moderation (one version per package in the queue), and the manifests PR, which runs after the push, never opened (#123 was made by hand). The `packages` job now opens the manifests PR right after updating the manifests, then packs and pushes to Chocolatey; a failed push still fails the job so it is re-run when the queue clears. RELEASING.md documents the behaviour.
Closes #129.
Tested: actionlint clean (the steps are unchanged, only reordered; the PR step's `add-paths` keeps the ignored `artifacts/` out of the commit).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On v1.1.0 the Chocolatey push failed with HTTP 403 because chocolatey.org still held 1.0.1 in moderation (one version per package in the queue), and the manifests PR, which runs after the push, never opened (#123 was made by hand). The
packagesjob now opens the manifests PR right after updating the manifests, then packs and pushes to Chocolatey; a failed push still fails the job so it is re-run when the queue clears. RELEASING.md documents the behaviour.Closes #129.
Tested: actionlint clean (the steps are unchanged, only reordered; the PR step's
add-pathskeeps the ignoredartifacts/out of the commit).🤖 Generated with Claude Code