Repair weekly community-base release advisory uv bootstrap

Open
  • Is something wrong?
#474 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, python
Domain
ci-cd, devops

Research direction

Read .github/workflows/release-advisory.yml alongside scripts/check_community_base_release.py; inspect the comparison step and its exit-code handling first. Check how the workflow bootstraps uv and Python on a bare GitHub-hosted runner, then verify exits 0, 2, and an error preserve the documented outputs and advisory path. Done means the bootstrap works while the release decision, error behavior, schedule, permissions, and deduplication remain unchanged.

Written by the indexing model from the issue text.

Description

bug infra operations P1

Problem and operator outcome

Hub intake d264d7b9-d93a-41c0-b00d-1190462433a5: the weekly Community-base Release Advisory has failed before inspecting releases since at least 2026-09-28. Run 40330880123 fails in Compare the pinned tag with the latest release with uv: command not found and exit 127. Restore the advisory on a bare GitHub-hosted runner without changing its release-decision or error contract.

Normative references

  • DTC fixed requirements: Python commands use uv.
  • Development process: independent engineer, tester and PM gates; on-call owns post-push observation.
  • Verification policy: versioned verification plan and explicit evidence dispositions; screenshots are inapplicable to CI-only changes.
  • Existing workflow and stdlib-only inspection script define the preserved advisory behavior.
  • The operator explicitly authorizes this job's direct worktree HEAD:main push and dispatch, overriding the usual local-main merge route. No PR is requested.

Scope

Repair the bootstrap in .github/workflows/release-advisory.yml so uv and a compatible Python interpreter are available before invoking the comparison script. The inspected script uses only Python's standard library; installing application dependencies or changing the lockfile is unnecessary unless implementation demonstrates a concrete need. Keep any regression verification focused on this workflow contract.

Non-goals

  • No community-base adoption, dependency pin changes, script feature changes, or new runtime packages.
  • No schedule, permission, runner, deduplication, advisory-content, or unrelated CI policy changes.
  • No product pages, deployment, database, infrastructure provisioning, or AWS access. Never use the main-temp AWS profile or static key for this job.

Dependencies

None. This is an independent workflow repair. GitHub repository push/dispatch authority is already provided by the operator; no AWS credential is needed.

Acceptance criteria

  • Community-base Release Advisory installs uv before scripts/check_community_base_release.py runs and provides the interpreter/dependencies the script needs on a bare runner; other workflow behavior is preserved.
  • Comparison exit 0 still emits result=already and follows Already latest; exit 2 still emits result=newer and the correct latest, and reaches the existing deduplicated advisory path. Any other exit remains an error and fails the job without masquerading as either result.
  • After pushing the approved fix to main, dispatch this workflow on main. Record the exact commit and run URL. The run must finish green when already current, or finish through the intended newer-release advisory path; a genuine error does not satisfy acceptance.
  • Work starts in an isolated worktree based on current origin/main; push directly to main with no PR after independent tester and PM approval, then remove the task worktree and branch.
  • Finish the report under ~/tmp/agent-reports/, publish the sanitized Hub result requested by intake, and announce/release the claim on the messaging bus. Do not expose credentials or use main-temp AWS credentials.

Verification scenarios

Repository and operations
  1. Independently inspect step order and uv bootstrap. Run the advisory script in an isolated standard-library environment without project sync, confirming its real interpreter needs are met.
  2. Exercise the actual comparison shell for ALREADY_LATEST/0, NEWER/2, and an error exit. Verify output fields and exit status, including absence of advisory output on genuine errors. Confirm the schedule, permissions and deduplication condition are unchanged.
  3. Generate the repository verification plan and retain the exact base/head, graph/plan digests and component dispositions. Use focused workflow checks; do not manufacture screenshot evidence for this CI-only change. Explain any graph-driven broader requirements explicitly in the role handoff.
  4. After the authorized direct push, on-call dispatches/observes the workflow on main and verifies step results and the intended outcome. An error, cancellation or missing final verdict remains unresolved.
Browser and Django

No public HTML, Django runtime, model, view or browser flow changes. Screenshots and product-browser scenarios are not_applicable with that reason. No new Django feature test is needed for a workflow bootstrap.

Dominant language
Python
Stars
0
Forks
0
Avg merge
32m
Merged PRs (30d)
8

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DataTalksClub/website

All issues in DataTalksClub/website

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.