Skip to content

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

Closed
github-actions[bot] wants to merge 2 commits into
mainfrom
github-actions/nightly-upgrade/semgrep
Closed

semgrep: Add versions 1.175.0, 1.175.1, 1.176.0, 1.176.1, 1.177.0#2044
github-actions[bot] wants to merge 2 commits into
mainfrom
github-actions/nightly-upgrade/semgrep

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 17, 2026

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

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

@github-actions
semgrep: Add versions 1.175.0, 1.175.1, 1.176.0, 1.176.1, 1.177.0
8efc6ac 
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@luhenry luhenry closed this Sep 17, 2026
@luhenry luhenry reopened this Sep 17, 2026
@luhenry
luhenry force-pushed the github-actions/nightly-upgrade/semgrep branch from 74bac3a to 105de0b Compare September 18, 2026 05:48
@github-actions

github-actions Bot commented Sep 18, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author
PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-09-20 16:19 UTC

@luhenry
semgrep: add riscv64 patches and fix checkout for untagged versions
290b533 
Squashes the prior three fix commits (add 1.175.0/1.176.0/1.177.0
patches, fix checkout ref resolution for 1.175.1/1.176.1, fix
Upstream-Status formatting) into one clean commit on top of the
bot's original version-declaration commit.

check_patch.py validates each patch file's Upstream-Status format as
introduced by the specific commit that added it (git diff-tree per
commit in the PR's history), not just the final tree state -- so an
earlier commit that added a badly-formatted patch still fails
validation even after a later commit fixes it. Squashing ensures no
commit in this branch's history ever introduces a malformed patch.

Signed-off-by: Ludovic Henry <git@ludovic.dev>
@luhenry Claude

luhenry commented Sep 19, 2026

Copy link
Copy Markdown
Member

semgrep 1.177.0 manylinux_riscv64 failure — investigated, not a workflow bug

Job 105623366770 fails with unknown type name 'version' compiling parser.c for ~33 tree-sitter language grammars (promql, protobuf, move_on_sui, move_on_aptos, circom, python, cpp, ocaml, go, ... — essentially the whole languages/ tree). Each parser.c is a literal Git LFS pointer stub instead of generated C source. The later make: *** [Makefile:115: core] Error 1 is the same failure surfacing after make finishes its parallel work — not a separate ocaml-compiler issue.

Root cause (verified upstream, not our checkout config):

  • git lfs ls-files against a fresh v1.177.0 checkout confirms all these parser.c files are unresolved LFS pointers.
  • There is no .gitattributes anywhere in the tree wiring *.c/these paths to the lfs filter, so lfs: true on actions/checkout (or a manual git lfs pull) would not smudge them — nothing tells git-lfs these paths are LFS-managed.
  • Directly querying GitHub's LFS media CDN for one of the objects (media.githubusercontent.com/media/semgrep/semgrep/<commit-sha>/languages/promql/.../parser.c) returns a genuine 404 MISS — the real blob was never uploaded to GitHub's LFS store for this tag.
  • Upstream's develop branch has real generated C source at the same paths today, so this was fixed after the tag was cut — but the v1.177.0 tag itself is immutable and permanently broken.
  • This only affects 1.177.0: v1.175.1/v1.176.1 build from the v1.175.0/v1.176.0 tags (per the untagged-version fix already in this PR), and v1.175.0/v1.176.0 predate this breakage.

This is a genuine upstream release defect (LFS objects never pushed for the v1.177.0 tag), not something a workflow/checkout change on our side can fix, and not a transient LFS bandwidth/rate-limit issue (re-running would fail identically every time). No code change pushed.

Options for a maintainer: drop the 1.177.0 entry from docs/packages/semgrep.yaml until upstream ships a fix/retag (e.g. v1.177.1), or point SEMGREP_REF at a specific later develop commit known to fix these files while still matching 1.177.0 — the latter needs care since develop isn't tag-aligned (its __VERSION__ currently reads 1.176.0).

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_011RwtHNpuiuiCk4MstTLu8m

Generated by Claude Code

@luhenry
luhenry force-pushed the github-actions/nightly-upgrade/semgrep branch 2 times, most recently from 4ee4f8d to 290b533 Compare September 19, 2026 18:29
@luhenry luhenry closed this Sep 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@threexc threexc Awaiting requested review from threexc
@justeph justeph Awaiting requested review from justeph
@luhenry luhenry Awaiting requested review from luhenry

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@luhenry