Skip to content

add support for zig#6

Open
omkarbhad wants to merge 36 commits into
opengrep:opengrep/mainfrom
omkarbhad:omkar/add-zig
Open

add support for zig#6
omkarbhad wants to merge 36 commits into
opengrep:opengrep/mainfrom
omkarbhad:omkar/add-zig

Conversation

@omkarbhad

@omkarbhad omkarbhad commented May 15, 2026 •
edited
Loading

Copy link
Copy Markdown

Summary

Adds Zig to the shared language registry as a development-stage language.

Registered extensions:

  • .zig
  • .zon

example_ext is set to .zig so snippet-to-file generation uses normal Zig source files rather than .zon build config files.

Scope

This PR only updates semgrep-interfaces.

It does not change opengrep behavior until opengrep bumps this submodule and adds the matching parser/language wiring.

Future opengrep work is tracked in omkarbhad/opengrep-zig, which provides the Zig tree-sitter language repo needed for the eventual full Zig support PR.

Sequencing Note

When opengrep consumes this change, the submodule bump must be paired with working Zig parser dispatch or an explicit rejection path. Otherwise -lang zig could become accepted before Zig scans produce meaningful parser results.

Verification

  • Ran python3 ./generate
  • Confirmed only the expected generated registry files changed:
    • generate.py
    • Language.ml
    • Language.mli
    • lang.json
  • Ran opam exec -- ocamlc -c Language.mli && opam exec -- ocamlc -c Language.ml

brandonspark and others added 30 commits December 12, 2024 09:05
@brandonspark
chore(ast-generic): Add Cls variant (semgrep#329)
1c82453 
- [X] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [X] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@aaronmichaelacosta
feat: added cocoapods lockfile to the list of supported lockfiles (se…
632b1de 
…mgrep#330)

Added necessary interface changes to support 1) a new ecosystem,
cocoapods, 2) new lockfile + manifest types for cocoapods, and 3) a new
parser type for (you guessed it) cocoapods.

- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!

Co-authored-by: Aaron Acosta <aaronacosta@aarons-mbp.local.meter>
@mjambon
Rename type xlang -> analyzer (semgrep#331)
48eb841 
This is part of renaming the OCaml module `Xlang` to `Analyzer`. This
type name change doesn't change the data format because type names don't
occur in JSON data.

- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@aryx
cleanup semgrep ci config section (semgrep#334)
aec607b 
test plan:
make


- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!

Co-authored-by: pad <pad@r2c.dev>
@aryx
simplify the RPC for SARIF (semgrep#336)
b54e43b 
The goal is to make it as close as possible as the general
CallFormat so at some point we can merge them.

test plan:
see related PR in semgrep


- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!

Co-authored-by: pad <pad@r2c.dev>
@brandonspark
chore: add id_info to ImportFrom (semgrep#332)
1d13c0e 
As title.

It seems that our `Makefile` is improperly specified and does not
regenerate `ast_generic_v1.py`. I fixed this in this PR also.

- [X] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [X] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@bkettle
chore(sca): add flag to disable subproject change detection (semgrep#335
147dcde 
)

Adds a new flag to pass from the app to the CLI that forces the CLI to
resolve
dependencies for all subprojects, all the time (even for diff scans).
Some
customers want this so that we get a full picture of their dependencies
for
every branch.

- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@aryx
Remove semgrep_version from project_metadata and meta from scan_reque…
41bdd7f 
…st (semgrep#333)

The backend should not use those fields anymore so
we can remove them. Note that even if old versions
of semgrep are still producing those fields, it is fine
because when the backend is consuming the JSON, any unknown
field is skipped and those fields should not be used anymore.

test plan:
see related PR in semgrep


- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!

Co-authored-by: pad <pad@r2c.dev>
@aryx
Adjust comments about deployment_config and semgrep ci HTTP requests (s…
705ebb0 
…emgrep#338)

test plan:
wait for green CI checks and see related PR in semgrep


- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!

---------

Co-authored-by: pad <pad@r2c.dev>
@aryx @mjambon
Remove ast_generic_v1.atd (semgrep#340)
a8fc7ca 
It was experimental and it's not maintained nor used, so
let's get rid of it.

test plan:
see related PR in semgrep


- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!

Co-authored-by: pad <pad@r2c.dev>
Co-authored-by: Martin Jambon <github@mjambon.com>
@mjambon
New input type for semgrep-core allows taking scanning roots instead …
5e0c767 
…of target files (semgrep#337)

This is used by
https://github.com/semgrep/semgrep-proprietary/pull/2878.

- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@brandonspark
feat(scrat): symbol analysis (semgrep#341)
13a74c5 
This PR adds "symbol analysis", a dump of the third-party symbols used
by a project, to the scan results for Semgrep.

This will enable the `scrat` project.

- [X] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [X] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@aryx @bkettle
New sca_match_kind and CallTransitiveReachable RPC v0 (semgrep#342)
2ec9015 
test plan:
see related PR in semgrep


- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!

---------

Co-authored-by: Ben Kettle <ben@semgrep.com>
@brandonspark
chore: add symbol analysis to scan config (semgrep#343)
3c94e14 
As title.

- [X] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [X] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@brandonspark
feat: upload symbol analysis (semgrep#344)
3e7d48a 
These are the relevant changes so we can plumb the symbol analysis
information through to upload it to the App.

- [X] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [X] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@brandonspark
pysemgrep upload symbol analysis (semgrep#346)
12be254 
This adds some stuff which makes us able to call uploading symbol
analysis from pysemgrep.
 
- [X] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [X] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@brandonspark
fix: erroneous comment in interface (semgrep#349)
3a9f93e 
Just fixed a typo, the return value is not an error message, it only
returns in the success case. It's a success message.
@nmote
Add GetTargets semgrep-core RPC (semgrep#347)
56950a4 
- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!

Co-authored-by: Martin Jambon <martin@semgrep.com>
@aryx
Define new sca_error intermediate type and sca_resolution_error and S…
2a998e7 
…caParseError (semgrep#350)

test plan:
see related PR in semgrep


- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@aryx
Complete the dependency_source type with MultiLockfile (semgrep#351)
d0803ee 
The goal is to remove the redundancy between the type defs
in the .atd and in subproject.py (which will help migrate
the code from subproject.py to a new Subproject.ml)

test plan:
see related PR in semgrep


- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@kopecs
chore: add LICENSE (semgrep#352)
d413564 
We previously did not distribute a specific license file with this
repository since it is included in semgrep/semgrep as a submodule, but
for clarity as to how this specific set of files is licensed (and
because users may obtain them separately) let's add a copy of the
license here.

Closes semgrep/semgrep#10850.
@bkettle
chore(sca-rpc): add internal dependency type (semgrep#345)
7efe189 
We need a different type to represent a dependency graph that is internal to
the Semgrep CLI. We already have these types in Python and in Ocaml. This adds
a corresponding type to the ATD interface so that the internal dependency type
can be sent via RPC.

- [x] I ran `make setup && make` to update the generated code after editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of the CLI.
      For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
      See https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!

      This updates only the RPC types, so is backwards compatible.
    

Towards SC-2082.
@bkettle
chore(tr): add dependency graph to TR rpc interface (semgrep#348)
47b9407 
TR will require sending the dependency graph in addition to the
transitive findings in order to do the filtering step. This adds a
single dependency graph to the RPC interface.

- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@aryx
Define Subproject datastructure in ATD (from subproject.py) (semgrep#354
98ddeee 
)

test plan:
see related PR in semgrep


- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@kopecs
feat: expose metavariable-name.modules (semgrep#355)
b9aa66e 
Allows `metavariable-name` to appear without a `semgrep-internal` prefix
when using the `module(s)` constraint (but not yet for `kind`).
@salolivares
feat(sca): add setup.py manfest type (semgrep#357)
dbb1f2f 
This PR adds the setup.py manifest type!

Towards SC-2149

- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@mjambon
Remove depth_diff field that's irrelevant to target selection (semgre…
571c38d 
…p#358)

This is for https://github.com/semgrep/semgrep-proprietary/pull/3099

- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@bkettle
chore(sca): tweak unresolved version (semgrep#359)
908e8c1 
Add "disabled" option to `UnresolvedReason` and make it a frozen
dataclass so we
can use it in sets and as a dictionary key in python

- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@bkettle
chore(tr): add option to resolve rpc to install dep source (semgrep#360)
f7da3e3 
Adds an option to the `ResolveDependencies` RPC to instruct the resolver
to
download dependency source code.

- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@salolivares
feat(sca): add unresolved reason and errors to subproject stats (semg…
e4e6f32 
…rep#356)

In semgrep/semgrep-proprietary#2872, we updated
the SCA subproject logic to scan only changed subprojects in diff scans.
Subprojects that remained unchanged were intentionally left unresolved
with the reason UnresolvedSkipped.

Previously, we didn't include this information in our subproject stats,
leaving us without visibility into why a subproject was unresolved. This
PR introduces two optional fields, unresolved_reason and errors,
allowing us to capture more granular stats and better understand
subproject resolution failures.

- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
ajbt200128 and others added 6 commits March 6, 2025 13:41
@ajbt200128
chore: use opam to simplify makefile (semgrep#361)
dee4b8b 
Let's install check-jsonschema via depexts!
See semgrep/semgrep-proprietary#3273 for more
context

- [X] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [X] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@aryx
Define TR caching comms in ATD (semgrep#353)
488ac75 
To make things more concrete about the interface we want
with the backend.

test plan:
make


- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@aryx
Add Opam ecosystem (semgrep#363)
be813cf 
This will allows us to dogfood SSC and TR with
Opam packages on the semgrep-pro repo

test plan:
see related PR in semgrep


- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@mmcqd
Replace lockfile with dependency source in targets (semgrep#362)
6edf9cf 
- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@bkettle
chore(sca): add rpc to match subprojects (semgrep#364)
74bee1e 
Adds an RPC type that allows Python to ask Ocaml to match subprojects
based on a list of dependency source files.
This will allow us to switch to ocaml-based subproject matching
independently from the rest of file targeting.

- [x] I ran `make setup && make` to update the generated code after
editing a `.atd` file (TODO: have a CI check)
- [x] I made sure we're still backward compatible with old versions of
the CLI.
For example, the Semgrep backend need to still be able to *consume* data
	  generated by Semgrep 1.50.0.
See
https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades
	  Note that the types related to the semgrep-core JSON output or the
	  semgrep-core RPC do not need to be backward compatible!
@omkarbhad
add support for zig
be8a45e 
Register Zig as a development-stage language with .zig and .zon extensions.

This only updates the shared language registry. It does not change
opengrep behavior until the opengrep repo bumps this submodule and wires
the matching Lang.Zig/parser dispatch.

When opengrep consumes this change, the submodule bump must be paired
with working Zig parser dispatch or an explicit rejection path so users
do not get accepted -lang zig scans with empty parser results.
@dimitris-m dimitris-m changed the base branch from main to opengrep/main June 23, 2026 11:46
@dimitris-m

dimitris-m commented Jun 23, 2026 •
edited
Loading

Copy link
Copy Markdown

Changed the base to opengrep/main which is the actual branch we use, sorry for any inconvenience.

@dimitris-m

dimitris-m commented Jun 23, 2026

Copy link
Copy Markdown

Please rebase onto opengrep/main. Conflicts should be minimal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.