Skip to content

[R3][MED] autoflow:release-dispatch sends undeclared workflow inputs; guaranteed 422 after pushing main #484

Description

@SisyphusZheng

Source: third full-project audit (2026-07-25). Severity: MEDIUM. Category: half-fix regression (workflow inputs removed in 8b220d43, dispatcher not updated).

Evidence

  • tools/autoflow/mod3.ts:620-640 — pushes origin main first, then gh workflow run autoflow-release.yml -f version=... -f plan=minor -f approvedPlan=....
  • .github/workflows/autoflow-release.yml:5-13 — declares only version and dry_run (git show 8b220d43 -- .github/workflows/autoflow-release.yml removed plan/approvedPlan).
  • GitHub returns 422 "Unexpected inputs provided" for undeclared workflow_dispatch inputs → the dispatch fails after main was already pushed, leaving a pushed-but-unpublished half state.
  • The current release flow (release-prepare → merge to main → publish-existing) bypasses this path, so it is a latent trap rather than an active failure. deno.json:108 autoflow:release-dispatch leads straight to it.

Suggested fix (decision needed)

Either delete the legacy command cluster (release-dispatch, release, patch-release, minor-plan tasks + mod3 branches) now that publish-existing is the supported flow, or align the dispatch inputs with the current workflow contract (version/dry_run only).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions