Skip to content

Conversation

@DoDoENT
Copy link
Contributor

@DoDoENT DoDoENT commented Nov 25, 2025

No description provided.

@DoDoENT
Copy link
Contributor Author

DoDoENT commented Nov 25, 2025

@bazel-io skip_check unstable_url

@bazel-io
Copy link
Member

Hello @Vertexwahn, modules you maintain (libpng) have been updated in this PR.
Please review the changes. You can view a diff against the previous version in the "Generate module diff" check.

@bazel-io bazel-io added the skip-url-stability-check Skip the URL stability check for the PR label Nov 25, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds support for libpng version 1.6.51. The overall structure is good, but there are a couple of issues that need to be addressed. Firstly, there's a misconfiguration in source.json where it mixes the modern overlay/ directory mechanism with the legacy overlay field, which will likely cause failures. Secondly, the main MODULE.bazel file for the BCR entry is overly verbose; it should be simplified by removing dependency declarations, which belong in the MODULE.bazel file within the overlay. I've provided specific suggestions to resolve these issues.

Comment on lines +4 to +8
"strip_prefix": "libpng-1.6.51",
"overlay": {
"BUILD.bazel": "sha256-12C6LaW6jdwqJzGfBe4LmbhS0rpaJ9UilhDArScYV0E=",
"MODULE.bazel": "sha256-WtQb+OE1ZVGBv6xUyXMFxwJOQGDBmZWixqVt+wB1kNk="
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

There's a configuration issue here that mixes two different overlay mechanisms. The PR correctly uses the modern overlay/ directory, which is supported by Bazel versions >=7.2.1 (as specified in bazel_compatibility). This makes the legacy overlay field in this source.json file both redundant and incorrect, as it points to files that don't exist at the expected location for this mechanism.

This will likely cause presubmit failures. To fix this, please remove the overlay field and rely solely on the overlay/ directory.

    "strip_prefix": "libpng-1.6.51"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When did this field become deprecated? I see all other modules are still having it.

Comment on lines +1 to +11
module(
name = "libpng",
version = "1.6.51",
bazel_compatibility = [">=7.2.1"], # need support for "overlay" directory
compatibility_level = 1,
)

bazel_dep(name = "platforms", version = "1.0.0")
bazel_dep(name = "rules_cc", version = "0.2.14")
bazel_dep(name = "rules_license", version = "1.0.0")
bazel_dep(name = "zlib", version = "1.3.1.bcr.7")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The MODULE.bazel file at the root of a version directory in the BCR should be minimal. It primarily serves as an entry point for bzlmod and should not declare the library's own dependencies. The dependencies required to build libpng (platforms, rules_cc, rules_license, zlib) should be declared only in the MODULE.bazel file that is overlaid into the source archive (i.e., overlay/MODULE.bazel).

Including them here can cause Bazel to process these dependencies twice. The bazel_compatibility attribute is also unnecessary in this file and belongs in overlay/MODULE.bazel.

Please simplify this file as suggested.

module(
    name = "libpng",
    version = "1.6.51",
    compatibility_level = 1,
)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can a human check this suggestion? So far, whenever I had a different MODULE.bazel files within the overlay and in the root, I got build issues.

- ubuntu2204
- ubuntu2404
- windows
bazel: [7.x, 8.x, rolling]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change this to bazel: [7.x, 8.x, 9.*]. rolling will use Bazel 10 prerelease.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done, but now the maintainer needs to approve the change in order for CI to re-run.

@DoDoENT DoDoENT force-pushed the feature/libpng-1.6.51 branch from 24ddc66 to 46cce94 Compare November 27, 2025 08:59
@Vertexwahn
Copy link
Contributor

@meteorcloudy Can you approve?

Copy link
Member

@bazel-io bazel-io left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All modules in this PR have been approved by their maintainers. This PR will be merged if all presubmit checks pass.

@Vertexwahn
Copy link
Contributor

@kotlaja Can you approve?

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

Labels

skip-url-stability-check Skip the URL stability check for the PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants