Repository navigation
Conversation
…ractice flow Every action pin in ci.yml, docs.yml and publish.yml was two majors behind and GitHub annotated each green run with a Node 20 deprecation notice nobody read. Bumped to the Node 24 majors; a Dependabot config (target dev, monthly, grouped) keeps them from rotting again. CONTRIBUTING has required `scripts/check_pathway_integration.py` to exit 0 before merge since the pathway template landed, but CI never ran it. It does now. docs.yml built on PRs to dev but not on pushes to dev, so the integration branch carried less evidence than main. Push trigger added; deploy stays gated on main. scripts/release_check.sh asserted __version__ == "0.1.0" and ran three test files. It has failed silently on every release since 0.2.0; it now reads the version from pyproject.toml and runs the full suite. Verified locally end to end. Also: a default pull-request template (the pathway one only applied with a ?template= query), CONTRIBUTING sections on hotfix sync-back and releasing (f0199c8 sat on main alone until this pass fast-forwarded dev), the packs/COVERAGE.md path corrected in two places, and ROADMAP Phase 1 checkboxes brought up to what actually exists. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…e it in the release step Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Private vulnerability reporting enabled on the repository the same day. SECURITY.md draws the line this project needs drawn: a wrong number is the worst bug we have, but it is a public evidence issue, not a private report. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
QA pass over the repository on 2026-09-07. Every CI gate was green locally and remotely; the defects were in the scaffolding around the gates rather than the gates themselves.
dev) keeps them current.check_pathway_integration.pyrequired by CONTRIBUTING, never run by CI. Added to the test job.devbut not on pushes todev. Push trigger added; deploy still gated onmain.release_check.shpinned to0.1.0and ran three test files. Now readspyproject.tomland runs the suite. Verified end to end locally.?template=), CONTRIBUTING sections on hotfix sync-back and releasing,packs/COVERAGE.mdpath fixed in two places, ROADMAP Phase 1 checkboxes made truthful.Alongside this PR a
ci-requiredruleset onmainanddevrequires a pull request and these checks: separation gate, test 3.11/3.12/3.13, Coverage, docsbuild. Admin bypass on PR only.Checks I ran locally
mkdocs build --strict,build_notebooks.py --check, cookbook testsscripts/release_check.sh(the corrected version)🤖 Generated with Claude Code