Skip to content

v0.3.0

Latest
Latest

Choose a tag to compare

View all tags
@qte77 qte77 released this 22 May 17:29
Immutable release. Only release title and notes can be modified.
v0.3.0
4a07dd2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Highlights

  • Error-handling boundary — when the action hits an auth/API failure (missing permissions: models: read, expired PAT, fork-PR read-only token, rate limit, upstream 5xx, network error) it now posts a ### Triage failure sticky comment to the triggering issue with a concrete fix, and the workflow stays red. See docs/integrations.md#troubleshooting for the per-class table. (#83, #84, #85)

  • Label rename — aligns with GitHub defaults:

    • good-first-issue → good first issue
    • needs-discussion → needs discussion
    • new documentation label added to the bot's vocabulary

    Legacy hyphenated spellings auto-removed from issues on next triage via DEPRECATED_LABELS reconciliation — no manual cleanup needed. (#79, closes #71, #63)

  • apps/claude recommendation removed from docs/integrations.md — over-privileged + misleading attribution. Full rationale in #68 and qte77/ai-agents-research#163. (#78)

  • Quieter consumer logs — setup-uv cache-dependency-glob pinned to action's own uv.lock instead of the consumer repo (silences the misleading "No file matched … cache will never get invalidated" warning). (#81, closes #65)

What's also in this release

  • docs/architecture.md — boundary failure-policy table (fail-loud / wrap-degrade / wrap-comment-fail-loud) per py-harden-ruff.md section 5. (#83)
  • AGENTS.md — concise governance file for AI agents contributing to this repo.
  • .github/dependabot.yaml + .github/workflows/codeql.yml. (#73)
  • Injection-safety comment in action.yaml. (#77)
  • Ruff select expanded (baseline + quality + TRY rule sets; strictness deferred to #62). (#82)
  • Live Dependabot status badge in README. (#72)
  • All workflow uses: SHA-pinned per repo strict-pin policy. (#60)

Migration notes

  • Caller workflows: no breaking changes; existing usage continues to work.
  • Label set: if your repo had the old hyphenated good-first-issue or needs-discussion labels applied by this action, they will be removed from issues on next triage. The new spaced spellings will be created if absent.
  • README Usage example updated to qte77/gha-issue-triage@v0.3.0. For strict-pin orgs, pin to this commit SHA: 4a07dd23bdd6bafc625bce6430f0aa5990fc327d.

Full changelog: CHANGELOG.md.

Assets 3
Loading