Skip to content

docs: refresh MAINTENANCE_RELEASE.md — stale since 2026-07-16 #229

Description

@ulises-jeremias

Summary

docs/MAINTENANCE_RELEASE.md was last updated on 2026-07-16 (61 days ago), exceeding the 60-day freshness threshold in the maintenance runbook.

What changed since the last update

Since 2026-07-16, the following release-relevant changes have happened:

  • v0.3.0 released (2026-09-10) — new CLI features (--json, --category, --config, --skip-install, Rich spinner, shell completion docs) shipped successfully. The release document should be verified against the actual v0.3.0 release workflow.
  • Docker GitHub Actions bumped — docker/setup-qemu-action 4.2→4.3, docker/setup-buildx-action 4.2→4.3, docker/login-action 4.5→4.6. The doc may reference old action versions or constraints.
  • MegaLinter upgraded from v9 to v10 — this affects the CI gate described in the publish sequence.
  • Two releases in this period (0.2.12 and 0.3.0) with a 6-week gap between them. The doc should reflect any lessons from the actual release cadence.

Suggested refreshes

  1. Verify the PyPI OIDC publish sequence steps match the current .github/workflows/release.yml.
  2. Update any Docker action version references or minimum version notes.
  3. Note the Docker race fix status — confirm whether the CDN sync wait is still required or was resolved upstream.

Acceptance criteria

  • PyPI OIDC publish sequence matches current release.yml
  • Docker action versions and race-fix notes are current
  • v0.3.0 release experience is reflected (any new friction points or improvements)

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

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions