Skip to content

Format files with Runic 1.10 - #5046

Merged
ChrisRackauckas merged 1 commit into
SciML:masterfrom
ChrisRackauckas-Claude:agent/runic-format-drift
Aug 30, 2026
Merged

Format files with Runic 1.10#5046
ChrisRackauckas merged 1 commit into
SciML:masterfrom
ChrisRackauckas-Claude:agent/runic-format-drift

Conversation

@ChrisRackauckas-Claude

Copy link
Copy Markdown
Member

Ignore this PR until it has been reviewed by @ChrisRackauckas.

What changed and why

Runic v1.10.0, used by the repository CI action, rejects three files that were clean under the previously installed local Runic v1.7.0. This PR applies only the v1.10.0 indentation changes so behavioral PRs do not need to mix mechanical formatting into their diffs.

Verification

$ Runic v1.10.0 --check .
exit 0

$ typos <three modified files>
exit 0

$ git diff --check
exit 0

GROUP=QA was not rerun after these whitespace-only changes. On clean upstream/master commit f9131984d9, it was run and failed with two existing package-wide checks: 263 JET typo-mode diagnostics and four unapproved public reexports. A separate investigation is in progress.

No docs build or behavioral test group was run because this PR contains only formatter output and changes no code behavior, public API, docstring, or documentation.

Unblocks the Runic check on #5045.

🤖 Generated with Codex (version unknown; model: unknown; session: local session ID 01a04feb-43da-7ce1-99e4-a68438c69833).

Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>

Co-Authored-By: OpenAI Codex <noreply@openai.com>

Agent-Harness: Codex (version unknown)

Agent-Model: unknown

Agent-Session: local session ID 01a04feb-43da-7ce1-99e4-a68438c69833
@ChrisRackauckas-Claude

Copy link
Copy Markdown
Member Author

Plan/status: apply only Runic v1.10.0 output to the three CI-identified files; verify the full tree with the exact formatter version; keep all behavior changes out of this mechanical PR; merge or otherwise land this cleanup before rebasing dependent PR #5045.

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.

2 participants