Skip to content

v0.3.0 - Independent launch blocker gate

Choose a tag to compare

View all tags
@lindixu6-hash lindixu6-hash released this 16 Aug 20:05
v0.3.0
2790816

A readiness score can now pass while explicit launch blockers still stop the release.

Added

  • opt-in fail-on-blockers Action input
  • independent score and launch-blocker gates
  • passed, blocker-count, and JSON blockers outputs
  • separate gate status and blocker list in the workflow summary
  • validation for malformed or empty blocker entries

Strict mode

- uses: lindixu6-hash/awesome-agentic-engineering@v0
  with:
    card: agent-card.json
    min-score: "15"
    fail-below: "true"
    fail-on-blockers: "true"

fail-on-blockers defaults to false for backward compatibility. Existing consumers keep their score-only behavior until they explicitly enable strict mode.

Verified

  • 46 automated tests pass
  • GitHub-hosted CI verifies that a 16/20 card passes its score gate but fails strict mode with two blockers
  • the failure step still exposes passed=false and blocker-count=2 for downstream diagnostics

中文：新增独立的上线阻塞项门禁。开启 fail-on-blockers: "true" 后，即使总分达标，只要 launch_blockers 非空，CI 仍会失败。该选项默认关闭以保持向后兼容，并新增综合结果、阻塞项数量和列表输出。

Verified adopter

Content OS Pipeline now runs both gates on main. Its public workflow run proves the score gate passes at 12/20 while strict mode exposes and fails on three unresolved launch blockers; the workflow then verifies SCORE_PASSED=true, AUDIT_PASSED=false, and BLOCKER_COUNT=3.

中文：首个采用项目已在 main 分支运行双门禁。总分门禁通过，但严格审计明确失败并暴露3个未解决阻塞项，同时保持整体审计工作流可验证。

Assets 2
Loading