Skip to content

Expose stable Bazel visibility target for generated scan#1123

Merged
ileitch merged 2 commits into
peripheryapp:masterfrom
brentleyjones:bj/bazel-generated-visibility
May 14, 2026
Merged

Expose stable Bazel visibility target for generated scan#1123
ileitch merged 2 commits into
peripheryapp:masterfrom
brentleyjones:bj/bazel-generated-visibility

Conversation

@brentleyjones
Copy link
Copy Markdown
Contributor

@brentleyjones brentleyjones commented May 1, 2026

Summary

Add a stable @periphery//bazel:generated package group that includes a generated-repo package group created at repository rule evaluation time. This gives Bazel projects a stable visibility label they can reference without depending on the generated scan package layout.

This is useful for --bazel-check-visibility, which disables Periphery's default --check_visibility=false behavior. With a stable wrapper target available, projects can grant visibility to Periphery's generated scan target explicitly and use checked visibility safely without relying on the ephemeral @periphery_generated root package.

Changes

  • add @periphery//bazel:generated as a stable package group wrapper
  • make @periphery_generated expose //visibility:package_group at repository-rule creation time
  • update the Bazel docs to point --bazel-check-visibility users at the stable wrapper target
  • add a changelog entry for the new visibility target

@brentleyjones
Copy link
Copy Markdown
Contributor Author

@ileitch

@ileitch ileitch merged commit 3125d42 into peripheryapp:master May 14, 2026
11 of 13 checks passed
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.

2 participants