chore: drop unused aspect_bazel_lib dependency#8
Merged
Conversation
aspect_bazel_lib was declared in MODULE.bazel but never loaded or referenced anywhere in the repo. Dropping it shrinks the dep graph with no behavior change. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Remove the
aspect_bazel_libbazel_depfromMODULE.bazel.Why
A grep across the repo (BUILD files,
.bzl, MODULE/WORKSPACE) finds zeroload("@aspect_bazel_lib//…")or@aspect_bazel_lib//…references — the dependency is declared but never used. Shrinking the dep graph removes a transitive fetch with no behavior change.Test plan
bazelisk build //...passes in CIexamples/rules_jstest step passes in CI🤖 Generated with Claude Code