Skip to content

semgrep: Add versions 1.175.0, 1.175.1, 1.176.0, 1.176.1, 1.177.0, 1.178.0 - #2283

Merged
luhenry merged 3 commits into
mainfrom
github-actions/nightly-upgrade/semgrep
Sep 25, 2026
Merged

luhenry merged 3 commits into
mainfrom
github-actions/nightly-upgrade/semgrep

Conversation

@riseproject-dev

Copy link
Copy Markdown
Contributor

Automatically generated by the nightly check_versions.py run.

semgrep v1.174.0 -> v1.175.0, v1.175.1, v1.176.0, v1.176.1, v1.177.0, v1.178.0

Every - version: entry added to docs/packages/semgrep.yaml is built by this PR's own build-semgrep.yml run; merging publishes the wheels.

…178.0

Signed-off-by: riseproject-dev[bot] <330740410+riseproject-dev[bot]@users.noreply.github.com>
@riseproject-dev
riseproject-dev Bot requested a review from luhenry September 24, 2026 07:18
@github-actions

github-actions Bot commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor
PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-09-25 05:21 UTC

…lve missing-tag versions to their .0 release
The v1.177.0 tag itself has 34 languages/*/tree-sitter/*/lib/parser.c files
checked in as literal Git LFS pointer stubs (upstream squash-merged the
per-language submodules into the main tree without resolving their LFS
objects first; fixed again at v1.178.0). No lfs:true/git-lfs-pull fixes
this since the tag's own .gitattributes never marks these paths for LFS -
a correct checkout produces exactly this pointer text, which then fails
`dune build`/`make core` with "unknown type name 'version'".

Add a repair step that reads a small per-version manifest
(lfs-pointer-fixups.tsv) and, for each still-broken file, re-fetches its
content from the exact commit the pre-merge submodule was pinned to at
v1.176.0 and verifies it against the pointer's own sha256 oid before using
it. No-op for every other version, which has no manifest.

gotcha 569
luhenry added a commit that referenced this pull request Sep 24, 2026
A release tag can check out clean and still hand a build Git LFS pointer
stubs instead of real content, when upstream squash-merges former
submodules into the main tree without resolving their LFS objects first
(the semgrep v1.177.0 case, PR #2283). The fix is content-addressable and
self-verifying: each pointer's own sha256 oid confirms a same-path fetch
from the pre-merge submodule's last pinned commit before it's trusted.
@luhenry
luhenry marked this pull request as ready for review September 24, 2026 23:24
@luhenry
luhenry merged commit 3f93fa6 into main Sep 25, 2026
19 checks passed
@luhenry
luhenry deleted the github-actions/nightly-upgrade/semgrep branch September 25, 2026 05:19
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.

1 participant