chore(deps): bump dtolnay/rust-toolchain from 3c5f7ea28cd621ae0bf5283f0e981fb97b8a7af9 to 2c7215f132e9ebf062739d9130488b56d53c060c - #4
Merged
Conversation
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
n1ckyb
added a commit
that referenced
this pull request
Aug 9, 2026
…test it (#19) The README example on this release candidate does not run: old = "def greet(name): return 'hi ' + name " The triple quotes had collapsed to single quotes, so it dies with "SyntaxError: unterminated string literal" at PARSE time, before importing anything. This is the first code a user copies, and it renders on PyPI. That is 0.0.1 defect #4 again, in a new form. 0.0.1's example raised NameError because it was a fragment; this one is self-contained but unparseable. Restored the triple quotes and confirmed it runs, printing exactly what the README claims two lines below it: ChangeType.ADDITION Insert -> if_statement('if_statement') ## The gate could never have caught this smoke_published_wheel.py already had "a real diff with a known-correct answer", but it ran OLD_SRC/NEW_SRC — the script's own PRIVATE copy of the example. That proves the library works. It proves nothing about what we published, which is precisely the gap that pulled 0.0.1: every check was green. So the gate now extracts the first ```python fence from the README a user reads and executes it against the INSTALLED wheel. Verified in both directions: repaired README exit 0 -> gate passes the broken RC README exit 1 -> gate catches it Found by auditing whether the RC actually contains the fixes 0.0.2 claims to ship, rather than assuming it did. The other three 0.0.1 defects are genuinely fixed on this branch. Co-authored-by: n1ckyb <nicknuxton@icloud.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Rebuilt on the current RC. The branch previously carried an older ci.yml, and a pull_request run uses the workflow from the PR's own branch - so it ran a version that predated the no-token degrade handling and failed with '--from-parser-artifacts needs GH_TOKEN or GITHUB_TOKEN', which Dependabot PRs can never satisfy because they receive no repository secrets. Net change against the RC is the pinned SHA only. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
n1ckyb
force-pushed
the
dependabot/github_actions/dtolnay/rust-toolchain-2c7215f132e9ebf062739d9130488b56d53c060c
branch
from
August 9, 2026 23:28
e56ed8e to
9ef654a
Compare
dependabot
Bot
deleted the
dependabot/github_actions/dtolnay/rust-toolchain-2c7215f132e9ebf062739d9130488b56d53c060c
branch
August 9, 2026 23:52
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.
Bumps dtolnay/rust-toolchain from 3c5f7ea28cd621ae0bf5283f0e981fb97b8a7af9 to 2c7215f132e9ebf062739d9130488b56d53c060c.
Commits
2c7215fAdd 1.97.1 patch releasefa04a14Add 1.96.1 patch release67ef31dUpdate actions/checkout@v6 -> v7Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)