bump scanner to SDK 0.6.x - #7
Merged
Merged
Conversation
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Greptile SummaryThe PR raises the default Unplug scanner dependency from the 0.4.x series to 0.6.x so consumers receive the newer scanner behavior.
Confidence Score: 5/5The PR appears safe to merge, with the dependency bump consistently applied and its intended scanner behavior covered by CI. The action, documentation, and CI use the same 0.6.x constraint, and the added fixtures exercise the behavior motivating the upgrade without exposing a concrete blocking failure.
|
| Filename | Overview |
|---|---|
| action.yml | Raises the default scanner constraint to the 0.6.x series while preserving the existing installation and invocation flow. |
| .github/workflows/ci.yml | Installs the new scanner range and adds focused fixtures for .github path filtering and missing-base-ref handling. |
| README.md | Keeps the documented action default and local installation command aligned with the new scanner range. |
Reviews (1): Last reviewed commit: "bump scanner to SDK 0.6.x + regression t..." | Re-trigger Greptile
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.
The action defaulted to
unplug-ai>=0.4.0,<0.5. The scanner fixes fromUnplugAI/Unplug#51 shipped in 0.6.0 on July 20, so every consumer has been
running the pre-fix scanner since then.
What 0.4.x misses, reproduced locally on the same repo state:
.github/agents/helper.mdCalledProcessErrortraceback, exit 1::error::, exit 2Injections straddling a 2000-char chunk boundary are also missed on 0.4.x;
0.6.0 uses a 200-char sliding overlap.
Bumps the default, the CI install, and the README to
>=0.6.0,<0.7.The existing CI fixtures use
.cursor/mcp.json, which 0.4.x detects fine, sothey passed the whole time. Added three cases that pin the floor to actual
behaviour:
.github/agents/is flagged (fails on 0.4.1).github/workflows/*.ymlstays out of scopeThe action-level preflight from #5 already covers the missing-base-ref case at
the wrapper. The chunking and
.github/gaps only exist in the SDK, so the pinwas the only thing keeping them open.