chore: update rhiza to v1.7.1 - #124
Merged
Merged
Conversation
The sync deleted docs/development/{TESTS,MARIMO}.md (superseded by the synced
docs/development/rhiza.md), docs/assets/rhiza-logo.svg (mkdocs-base.yml now points
at the upstream copy) and docs/paper/README.md (template scaffolding describing the
docs/paper layout; quadprog.tex and quadprog.bib are the real sources and stay).
stage_synced.py leaves those orphan deletions unstaged, so they are committed here
along with the mkdocs.yml nav entries that pointed at the removed pages -- without
that the new book-nav gate fails the build. Static Analysis is repo-owned and stays.
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
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.
Bumps the rhiza template from v1.6.0 to v1.7.1 (
jebel-quant/rhiza).What the sync did
14 template-owned files changed, 0 conflicts:
.github/workflows/rhiza_*.ymlre-pinned to@v1.7.1(includingrhiza_paper.yml).gitignore,.pre-commit-config.yaml,Makefile,docs/mkdocs-base.yml,.rhiza/template.lockdocs/development/rhiza.md— one page linking to the guides now published upstreamDeletions and the nav, folded in as a second commit
v1.7.1 deletes
docs/development/TESTS.md,docs/development/MARIMO.md,docs/assets/rhiza-logo.svganddocs/paper/README.md(template scaffolding describingthe
docs/paperlayout —quadprog.texandquadprog.bibare the real sources and areuntouched).
stage_synced.pystages only paths in the new lock, so these orphandeletions come out unstaged; they are committed here rather than left to dirty the tree.
mkdocs.yml(repo-owned) pointed its Development section atdevelopment/TESTS.mdanddevelopment/MARIMO.md. v1.7.1'srhiza_bookworkflow adds abook-navgate thatfails on any nav entry missing from
_book/, so both are replaced bydevelopment/rhiza.md.Static Analysisis repo-owned and stays. Verified locally —rhiza-task book && rhiza-task book-nav→ all 6 nav target(s) resolve, and the papertask still builds.
Not run
No gates were run here. Use
/rhiza:qualityfor a scorecard.