Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump rules_license to 1.0.0 #549

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

shs96c
Copy link
Contributor

@shs96c shs96c commented Oct 22, 2024

This brings in the purl field that is increasingly used by other libraries. In the bzlmod world this is less important, but for folks using workspace-based builds, skylib tends to be loaded early so any deps it brings in normally end up being used.

This brings in the `purl` field that is increasingly used by other
libraries. In the `bzlmod` world this is less important, but for
folks using workspace-based builds, skylib tends to be loaded early
so any deps it brings in normally end up being used.
@@ -11,7 +11,7 @@ register_toolchains(
)

bazel_dep(name = "platforms", version = "0.0.4")
bazel_dep(name = "rules_license", version = "0.0.7")
bazel_dep(name = "rules_license", version = "1.0.0")
Copy link

@brentleyjones brentleyjones Oct 28, 2024

Choose a reason for hiding this comment

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

Do we want to force 1.0.0 on people? I'm only asking because MODULE.bazel should declare the minimum version needed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It should be fine to update everyone to use 1.0.0: it's not hugely different from the previous release and I don't think it introduces new dependencies. OTOH, it includes the purl attribute in the PackageInfo which is useful when generating SBOMs

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