Repository navigation
Update SPDX license files (2026-10-28 04:17 UTC) - #172
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
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
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.
Warning
Do not push commits directly to this PR's
auto-update-licensesbranch or manually edit this description. The nightly workflow updates both and may overwrite manual changes. For changes that depend on this update, open a stacked PR withauto-update-licensesas its base. For generator or workflow fixes that must persist, open a separate PR againstmain, merge it, and rerun this workflow.This PR was generated by the fetch-licenses workflow from spdx/license-list-data.
3.29.05f58f4bSPDX changes
Licenses
Exceptions
Deprecations
License range families
Review instructions (human and Copilot)
Use the summary above as the expected change set and report any discrepancy between it, the source JSON, and the generated files. Focus review on these invariants:
-onlyIDs in the same version group, and is sorted in semantic version order.None, leave an inline review comment on the relevant generated family block beginning with Human review required: license range family changed.