Skip to content

Prepare p4c for submission to the Bazel Central Registry (#5455)#5497

Merged
smolkaj merged 1 commit into
mainfrom
bcr
Feb 24, 2026
Merged

Prepare p4c for submission to the Bazel Central Registry (#5455)#5497
smolkaj merged 1 commit into
mainfrom
bcr

Conversation

@smolkaj

@smolkaj smolkaj commented Feb 24, 2026

Copy link
Copy Markdown
Member

No description provided.

@smolkaj smolkaj requested a review from fruffy February 24, 2026 05:59
@smolkaj smolkaj marked this pull request as ready for review February 24, 2026 05:59
Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
@fruffy fruffy added the infrastructure Topics related to code style and build and test infrastructure. label Feb 24, 2026
@smolkaj smolkaj added this pull request to the merge queue Feb 24, 2026
@smolkaj

smolkaj commented Feb 24, 2026

Copy link
Copy Markdown
Member Author

On a related note @fruffy: any chance we are planning to cut a release any time soon?

And what's the general process around that (when do we cut releases in general, who or what triggers it)?

Merged via the queue into main with commit 18eba67 Feb 24, 2026
24 checks passed
@smolkaj smolkaj deleted the bcr branch February 24, 2026 18:56
@fruffy

fruffy commented Feb 24, 2026

Copy link
Copy Markdown
Collaborator

On a related note @fruffy: any chance we are planning to cut a release any time soon?

The releases are meant to be triggered monthly and this used to work... I am not sure what happened and why the CI run is failing. I thought we fixed it.

@chreekat Can you investigate?

@smolkaj

smolkaj commented Feb 27, 2026

Copy link
Copy Markdown
Member Author

@fruffy @chreekat I feel I saw an update on the release discussion somewhere? Cannot find it now. Perhaps I'm misremembering.

If this takes longer, would it be easy to cut a release manually as a one-off, since that would allow us to add p4c to the Bazel Central Registry?

@fruffy

fruffy commented Feb 27, 2026 via email

Copy link
Copy Markdown
Collaborator

smolkaj added a commit to smolkaj/bazel-central-registry that referenced this pull request Mar 2, 2026
p4c (https://github.com/p4lang/p4c) is the P4_16 reference compiler.
This is the first submission of p4c to the BCR, made possible by the
Bzlmod migration in v1.2.5.11 (p4lang/p4c#5454, p4lang/p4c#5497).

Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
smolkaj added a commit to smolkaj/bazel-central-registry that referenced this pull request Mar 2, 2026
p4c (https://github.com/p4lang/p4c) is the P4_16 reference compiler.
This is the first submission of p4c to the BCR, made possible by the
Bzlmod migration in v1.2.5.11 (p4lang/p4c#5454, p4lang/p4c#5497).

Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
smolkaj added a commit to smolkaj/bazel-central-registry that referenced this pull request Mar 2, 2026
p4c (https://github.com/p4lang/p4c) is the P4_16 reference compiler.
This is the first submission of p4c to the BCR, made possible by the
Bzlmod migration in v1.2.5.11 (p4lang/p4c#5454, p4lang/p4c#5497).

Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
smolkaj added a commit to smolkaj/bazel-central-registry that referenced this pull request Mar 2, 2026
p4c (https://github.com/p4lang/p4c) is the P4_16 reference compiler.
This is the first submission of p4c to the BCR, made possible by the
Bzlmod migration in v1.2.5.11 (p4lang/p4c#5454, p4lang/p4c#5497).

Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
smolkaj added a commit to smolkaj/bazel-central-registry that referenced this pull request Mar 2, 2026
p4c (https://github.com/p4lang/p4c) is the P4_16 reference compiler.
This is the first submission of p4c to the BCR, made possible by the
Bzlmod migration in v1.2.5.11 (p4lang/p4c#5454, p4lang/p4c#5497).

Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
smolkaj added a commit to smolkaj/bazel-central-registry that referenced this pull request Mar 3, 2026
p4c (https://github.com/p4lang/p4c) is the P4_16 reference compiler.
This is the first submission of p4c to the BCR, made possible by the
Bzlmod migration in v1.2.5.11 (p4lang/p4c#5454, p4lang/p4c#5497).

Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
smolkaj added a commit to smolkaj/bazel-central-registry that referenced this pull request Mar 3, 2026
p4c (https://github.com/p4lang/p4c) is the P4_16 reference compiler.
This is the first submission of p4c to the BCR, made possible by the
Bzlmod migration in v1.2.5.11 (p4lang/p4c#5454, p4lang/p4c#5497).

Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
keith pushed a commit to bazelbuild/bazel-central-registry that referenced this pull request Mar 3, 2026
## Description

Adds [p4c](https://github.com/p4lang/p4c) v1.2.5.11 — the P4_16
reference compiler — to the BCR. This is the first p4c submission, made
possible by the Bzlmod migration completed in this release
([p4lang/p4c#5454](p4lang/p4c#5454),
[p4lang/p4c#5497](p4lang/p4c#5497)).

## Module
- **Name:** `p4c`
- **Version:** `1.2.5.11`
- **Source:** https://github.com/p4lang/p4c/releases/tag/v1.2.5.11

## Notes

- The `inja` dependency is not yet in the BCR and is loaded via a module
extension defined in p4c's own `bazel/repositories.bzl`. This is
self-contained and requires no BCR changes.
- The `p4c_ir_extensions` module extension provides an opt-in mechanism
for downstream users to register custom IR extensions; it has no effect
unless explicitly used.
- Presubmit builds `@p4c//...` on Ubuntu 22.04 and 24.04 against Bazel
7.x, 8.x, and 9.x.

## Checklist

- [x] Module added under `modules/p4c/`
- [x] `metadata.json` with homepage, maintainers, and repository
- [x] `source.json` pointing to the release tarball with verified
SHA-256 integrity
- [x] `MODULE.bazel` with correct version
- [x] `presubmit.yml` covering Ubuntu 22.04/24.04 × Bazel 7/8/9

Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
ileitch pushed a commit to ileitch/bazel-central-registry that referenced this pull request Apr 7, 2026
## Description

Adds [p4c](https://github.com/p4lang/p4c) v1.2.5.11 — the P4_16
reference compiler — to the BCR. This is the first p4c submission, made
possible by the Bzlmod migration completed in this release
([p4lang/p4c#5454](p4lang/p4c#5454),
[p4lang/p4c#5497](p4lang/p4c#5497)).

## Module
- **Name:** `p4c`
- **Version:** `1.2.5.11`
- **Source:** https://github.com/p4lang/p4c/releases/tag/v1.2.5.11

## Notes

- The `inja` dependency is not yet in the BCR and is loaded via a module
extension defined in p4c's own `bazel/repositories.bzl`. This is
self-contained and requires no BCR changes.
- The `p4c_ir_extensions` module extension provides an opt-in mechanism
for downstream users to register custom IR extensions; it has no effect
unless explicitly used.
- Presubmit builds `@p4c//...` on Ubuntu 22.04 and 24.04 against Bazel
7.x, 8.x, and 9.x.

## Checklist

- [x] Module added under `modules/p4c/`
- [x] `metadata.json` with homepage, maintainers, and repository
- [x] `source.json` pointing to the release tarball with verified
SHA-256 integrity
- [x] `MODULE.bazel` with correct version
- [x] `presubmit.yml` covering Ubuntu 22.04/24.04 × Bazel 7/8/9

Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

infrastructure Topics related to code style and build and test infrastructure.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants