Skip to content

build(deps): bump rules_pkg from 1.2.0 to 1.3.0 - #22926

Open
dependabot[bot] wants to merge 4 commits into
mainfrom
dependabot/bazel/rules_pkg-1.3.0
Open

dependabot[bot] wants to merge 4 commits into
mainfrom
dependabot/bazel/rules_pkg-1.3.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Bumps rules_pkg from 1.2.0 to 1.3.0.

Commits

@dependabot dependabot Bot added bazel Pull requests that update bazel code dependencies Pull requests that update a dependency file labels Oct 28, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner October 28, 2026 19:05
@dependabot
dependabot Bot force-pushed the dependabot/bazel/rules_pkg-1.3.0 branch 3 times, most recently from ee96709 to 859f302 Compare November 3, 2026 15:20
@jketema

jketema commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

@dependabot rebase

@dependabot
dependabot Bot force-pushed the dependabot/bazel/rules_pkg-1.3.0 branch from 859f302 to 8add6cf Compare November 9, 2026 09:23
Copilot AI auto review requested due to automatic review settings November 9, 2026 09:23

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Changes recommended

Approval is blocked because the build-rule update affects shipped extractor artifacts and the review lacks DCA results for the final change or an assessment of regressions.

1 open issue
What changed in this PR

Updates the Bazel rules_pkg dependency from version 1.2.0 to 1.3.0 for the repository’s packaging targets.

Changes:

  • Bumps rules_pkg to version 1.3.0 in the Bazel module definition.
  • Preserves existing packaging consumers and repository references to the dependency.

This pull request requires changes.

File Summary
MODULE.bazel Updates the rules_pkg dependency to 1.3.0. Because this dependency is used by extractor packaging targets, include DCA results for the final change and assess any changed results or unexpected regressions.

Review effort: Lite (auto)

Comment thread MODULE.bazel
bazel_dep(name = "rules_go", version = "0.65.0")
bazel_dep(name = "rules_java", version = "9.9.0")
bazel_dep(name = "rules_pkg", version = "1.2.0")
bazel_dep(name = "rules_pkg", version = "1.3.0")
@jketema
jketema requested review from a team as code owners November 9, 2026 09:39
@jketema
jketema requested a review from a team as a code owner November 9, 2026 10:00
@jketema
jketema marked this pull request as draft November 9, 2026 12:45
@jketema
jketema removed request for a team November 9, 2026 12:46
@jketema

jketema commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

@dependabot rebase

@jketema jketema closed this Nov 9, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 9, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@jketema jketema reopened this Nov 9, 2026
@jketema

jketema commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

@dependabot rebase

@dependabot @github

dependabot Bot commented on behalf of github Nov 9, 2026

Copy link
Copy Markdown
Contributor Author

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

@jketema

jketema commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

@dependabot recreate

Bumps [rules_pkg](https://github.com/bazelbuild/rules_pkg) from 1.2.0 to 1.3.0.
- [Release notes](https://github.com/bazelbuild/rules_pkg/releases)
- [Changelog](https://github.com/bazelbuild/rules_pkg/blob/main/CHANGELOG.md)
- [Commits](bazelbuild/rules_pkg@1.2.0...1.3)

---
updated-dependencies:
- dependency-name: rules_pkg
  dependency-version: 1.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/bazel/rules_pkg-1.3.0 branch from 8b13e2e to 172d608 Compare November 9, 2026 12:58
Define the variable as its literal pack-routing placeholder in both Bazel configurations so rules_pkg 1.3 leaves it for CodeQL's later expansion.
@jketema
jketema force-pushed the dependabot/bazel/rules_pkg-1.3.0 branch from ee0a500 to c578e1f Compare November 9, 2026 14:29
@github-actions github-actions Bot added the Swift label Nov 9, 2026
Moving the C++ library target only aligns solib ownership in standalone builds. When CodeQL is a dependency, the solib artifacts still live in the root repository's runfiles but are owned by the CodeQL repository, so rules_pkg 1.3 cannot resolve them.

Overlay the extractor's runfiles with the original prebuilt shared libraries at the same installed destinations. This preserves package contents and permissions while using source paths that resolve correctly in both build layouts.
@jketema
jketema force-pushed the dependabot/bazel/rules_pkg-1.3.0 branch from f10126c to 281f38c Compare November 10, 2026 14:03
@jketema
jketema marked this pull request as ready for review November 10, 2026 15:20
@jketema
jketema requested a review from a team as a code owner November 10, 2026 15:21

This branch has not been deployed

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

Labels

bazel Pull requests that update bazel code dependencies Pull requests that update a dependency file Swift

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants