Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .github/CODEOWNERS
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
AGENTS.md @YoneRai12
.github/workflows/* @YoneRai12
clients/cli/yonerai_cli/services/realtime_sync_client_service.py @YoneRai12
docs/contracts/ @YoneRai12
8 changes: 8 additions & 0 deletions .github/workflows/quality-wall.yml
Original file line number Diff line number Diff line change
Expand Up @@ -268,8 +268,10 @@ jobs:
core/src/ora_core/execution/auto_runtime.py \
scripts/ci_quality_scans.py \
scripts/release_gate.py \
scripts/yonerai_release_gate.py \
tests/test_auth_privacy_policy.py \
tests/test_release_gate.py \
tests/test_yonerai_release_gate.py \
tests/test_ci_quality_scans.py
python -m compileall clients/cli/yonerai_cli core/src/ora_core scripts
- name: Run security boundary tests
Expand Down Expand Up @@ -308,6 +310,7 @@ jobs:
tests/test_verify_version.py \
tests/test_release_workflow_prerelease.py \
tests/test_release_gate.py \
tests/test_yonerai_release_gate.py \

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Run the new release gate in CI

Adding the new test file to the release-gate job only exercises unit tests; the job below still invokes scripts/release_gate.py and never executes scripts/yonerai_release_gate.py --fail-on-blockers, and the tag release workflow is likewise unchanged. As a result, the new #552/cross-repo blocker checks and release_go decision can be completely bypassed during CI/release, so a v0.23 release path can pass without consulting this governance gate.

Useful? React with 👍 / 👎.

tests/test_current_truth_anchor.py \
tests/test_quality_wall_workflow.py \
-q
Expand All @@ -334,3 +337,8 @@ jobs:
--tag "v${VERSION}" \
--github-prerelease auto
fi
- name: Run v0.23 cross-repo release gate snapshot
env:
GH_TOKEN: ${{ secrets.YONERAI_RELEASE_GATE_TOKEN || github.token }}
run: |
python scripts/yonerai_release_gate.py --release-issue 592
6 changes: 6 additions & 0 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -113,11 +113,17 @@ jobs:
PY

- name: Run Release Gate
env:
GH_TOKEN: ${{ secrets.YONERAI_RELEASE_GATE_TOKEN || github.token }}
run: |
python scripts/release_gate.py \
--tag "${GITHUB_REF_NAME}" \
--artifact "${PRODUCT_NAME}-${ORA_VERSION}.zip" \
--github-prerelease "${ORA_PRERELEASE}"
python scripts/yonerai_release_gate.py \
--release-issue 592 \

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Do not hard-code the v0.23 gate issue

This workflow runs for every pushed tag matching v*, but the new gate always checks issue #592. Once v0.23 has passed or a later release has its own gate issue, non-v0.23 releases will still be governed by stale #592 checklist/state instead of the release being built, and --fail-on-blockers can abort them for that unrelated issue; pass the issue number from release metadata/input or scope this hard-coded check to the v0.23 tag only.

Useful? React with 👍 / 👎.

--release-notes "docs/releases/${ORA_VERSION}.md" \
--fail-on-blockers

- name: Create GitHub Release
uses: softprops/action-gh-release@v1
Expand Down
Loading
Loading