Run tests in CI, and gate releases on them

[agarzon]

Nothing has ever run the tests in CI. .github/workflows/ held only publish.yml and release.yml, both triggered by a tag — so a red commit could reach the ComfyUI Registry, where it lands on real installs. The 293 backend tests only ever ran on a maintainer machine.

What this does

• test.yml — pytest -q plus node --test tests/test_upload.mjs, on pull_request and pushes to main. Also exposes workflow_call.
• release.yml / publish.yml — each gains a test job (uses: ./.github/workflows/test.yml) and needs: test. A red tag now ships nothing, to the Registry or to GitHub Releases.
• CLAUDE.md — the commands block still said "there is no JS test harness"; there is one as of Folder upload: drag a folder in, or pick one (#5) #9.

Choices

• Python 3.10, the floor in requires-python. One version, no matrix — add one when a version-specific bug actually bites.
• The node step names its file: node --test <dir> treats a directory it finds no tests in as a missing module and fails outright.
• No coverage gates, no lint job.

Known corner, accepted

The manual workflow_dispatch changelog-backfill path tests the dispatch ref (main) rather than the old tag being backfilled. Costs a minute, and can block a backfill while main is red — safe-fail, and not worth conditional gymnastics to avoid.

Verification

Both suites pass on this branch (293 passed / 1 skipped; 3 JS tests), and all three workflow files parse with the expected job graphs — test, test + publish, test + release. The gating itself only proves out on the next tag push.

[Copilot]

Pull request overview

Adds a dedicated CI test workflow and wires release/publish workflows to depend on it, preventing tags from publishing or releasing when tests fail.

Changes:

• Introduces .github/workflows/test.yml to run Python (pytest) and Node (node --test) test suites on PRs and pushes to main, and as a reusable workflow.
• Updates .github/workflows/release.yml to run the test workflow first and gate the release job on it.
• Updates .github/workflows/publish.yml to run the test workflow first and gate the publish job on it.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
.github/workflows/test.yml	Adds a reusable CI workflow that runs backend (pytest) and frontend (node test runner) tests.
.github/workflows/release.yml	Adds a test job and gates the release job on it.
.github/workflows/publish.yml	Adds a test job and gates the publish job on it.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[agarzon]

Done — python -m pip and python -m pytest, so both target the interpreter setup-python provisioned.

[agarzon]

Fixed, in both directions.

test.yml now declares permissions: contents: read at the workflow level, so every caller gets the reduced scope rather than each one remembering to pass it — this job runs repo code via pip install -e . and never writes anything back.

release.yml also had contents: write at the workflow level; that has moved onto the release job, which is the only thing that needs it to create the release.

[agarzon]

Correct, and it is a pre-existing bug rather than something this PR introduced — release.yml has always checked out the dispatch ref. publish.yml already pinned ref: ${{ github.event.inputs.tag || github.ref_name }}; release.yml now matches it.

Outside this PR's original scope, but it is two lines, the fix already existed in the sibling file, and leaving a known-wrong release-notes path in a file I am editing anyway is the worse call. Flagged in the PR description.

Note it does not extend to the reusable test job: a workflow_call job runs at the caller's ref, so a manual backfill still tests main. That corner is called out in the description as accepted.