Skip to content

chore(ci): enforce development and release verification - #139

Open
xjoker wants to merge 1 commit into
devfrom
codex/development-standards
Open

xjoker wants to merge 1 commit into
devfrom
codex/development-standards

Conversation

@xjoker

@xjoker xjoker commented Nov 18, 2026

Copy link
Copy Markdown
Owner

Why

Contributors and maintainers need a shared standard for closing Issues, verifying PRs, and deciding whether a commit is ready to release. PR #137 merged with failed checks, which showed that the existing guidance needed enforcement.

What changed

  • Add repository instructions for Issue closure and a PR template that records verification.
  • Verify the latest eligible dev CI for the exact release SHA before moving the rolling tag and in the Release workflow.
  • Document supported release channels and GitHub's private reporting path.

Scope

The repository changes cover contribution, release, and security reporting. The dev ruleset and private vulnerability reporting have already been enabled in repository settings.

Blast Radius

A candidate with missing or failed dev CI stops before the release build. The checker accepts a successful partial rerun when all four jobs have successful results for the same commit.

Verification

  • python3 -m unittest discover -s scripts/ci -p 'test_*.py' passed all 16 tests.
  • cargo test --locked --test test_distribution_contract passed all 35 tests.
  • Verified the gate with live Actions data. It accepted the passing release commit and rejected commits with failed or missing CI. Checked the release YAML and the shell commands in the release guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant