Skip to content

Conversation

@neilconway
Copy link
Contributor

@neilconway neilconway commented Sep 23, 2025

  • Upgrade to Bazel 7
  • Upgrade to rules_python 1.0.0 and fix breakage
  • Upgrade to protobuf 29.5
  • Use py_proto_library from the protobuf repo, not rules_proto (deprecated)
  • Use cc_proto_library from the protobuf repo, not rules_cc (deprecated)
  • Actually run the cpp test in bazel test
  • Remove repo_mapping cruft (isn't supported in modern Bazel versions anyway).

@aviator-app
Copy link

aviator-app bot commented Sep 23, 2025

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This PR is queued for merge (review queue position).

It will be merged when it reaches the top of the queue and all required status checks are passing.

Pending Status Checks


See the real-time status of this PR on the Aviator webapp.
Use the Aviator Chrome Extension to see the status of your PR within GitHub.

@aviator-app aviator-app bot added the blocked label Sep 23, 2025
@aviator-app
Copy link

aviator-app bot commented Sep 23, 2025

This pull request failed to merge: this PR has conversations which must be resolved before merging. After you have resolved the problem, you should remove the blocked pull request label from this PR and then try to re-queue the PR. Note that the pull request will be automatically re-queued if it has the mergequeue-ready label.

@aviator-app aviator-app bot added the blocked label Sep 24, 2025
@neilconway neilconway removed the blocked label Nov 6, 2025
@neilconway neilconway enabled auto-merge (squash) November 6, 2025 15:28
@neilconway neilconway disabled auto-merge November 6, 2025 15:28
* Upgrade to Bazel 7.7.0
* Upgrade to `rules_python` 1.0.0 and fix breakage
* Upgrade to protobuf 29.5
* Use `py_proto_library` and `ProtoInfo` from the protobuf repo, not
  `rules_proto` (deprecated); we also neglected to properly import the
  dependency on `rules_proto` anyway.
* Use `cc_proto_library` from the protobuf repo, not `rules_cc` (deprecated)
* Actually run the cpp test in `bazel test`
* Remove `repo_mapping` cruft (isn't supported in modern Bazel versions anyway).
As previously configured, no runner was ever started by GitHub (perhaps because
we were using ubuntu 20.04?).
@neilconway neilconway merged commit 6887bd9 into main Nov 11, 2025
2 checks passed
@neilconway neilconway deleted the neilc/bazel-upgrade branch November 11, 2025 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants