Skip to content

fix: move release-watch container to job level (#105) - #106

Merged
michael-conrad merged 1 commit into
devfrom
feature/105-job-level-container
Sep 25, 2026
Merged

michael-conrad merged 1 commit into
devfrom
feature/105-job-level-container

Conversation

@michael-conrad

Copy link
Copy Markdown
Owner

Summary

  • Move the release-watch container from step level to job level in .github/workflows/upstream-release-watch.yml — step-level container/entrypoint caused a live HTTP 422 Unexpected value container on dev (verified live)
  • Job now declares job-level container.image: ghcr.io/astral-sh/uv:python3.12-bookworm-slim with a uv run scripts/release-watch.py run step after checkout
  • permissions and on:/concurrency: untouched
  • Repair inverted assertion in test_sc2_checkout_step_precedes_script_invocation that passed only vacuously; add SC-6 state-advance test for run_release_watch()
  • 22/22 tests pass; live-dispatch SCs (SC-3/4/5/7) verify post-merge on dev per plan phases 2/3/4/6

Outcome

Release-watch workflow will run successfully on its weekly schedule instead of failing with HTTP 422.

Fixes #105


🤖 Co-authored with AI: OpenCode (ollama-cloud/glm-5.3-flash)

Move the release-watch container from the weekly trigger workflow
step level to the job level (SC-1, SC-2). Add SC-6 state-advance
enforcement test for run_release_watch() (pytest, mocked upstream
fetch and issue filing).

Co-authored with AI: OpenCode (ollama-cloud/glm-5.3-flash) <noreply@example.com>
Co-authored-by: Michael Conrad <m.conrad.202@gmail.com>
@michael-conrad
michael-conrad merged commit 31ca3dc into dev Sep 25, 2026
4 checks passed
@michael-conrad
michael-conrad deleted the feature/105-job-level-container branch September 25, 2026 02:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant