Skip to content

Record vendored licenses and split future syncs in two - #424

Merged
TheGreatAxios merged 2 commits into
mainfrom
vendoring-license-record
Aug 9, 2026
Merged

Record vendored licenses and split future syncs in two#424
TheGreatAxios merged 2 commits into
mainfrom
vendoring-license-record

Conversation

@TheGreatAxios

Copy link
Copy Markdown
Collaborator

The vendoring table recorded the upstream commit but not what license the code arrived under or when it was taken — both of which an audit needs, and neither of which is derivable from the hash alone. Adds them as columns, and notes that each vendored tree carries its own LICENSE untouched.

Also changes the re-sync procedure to land the pristine upstream copy and the re-applied patches as two commits rather than one. The unmodified upstream state then becomes a checkout instead of a reconstruction. The most recent sync landed as a single commit and does not have this property, which is what makes its patch ledger load-bearing rather than descriptive — the doc now says so.

An audit of a vendored tree needs to answer two questions the table could
not: what license the code arrived under, and when it was taken. The
license each package declares and the date the copy landed are now columns
beside the upstream commit that supplies the other half of the provenance.

The sync procedure now lands the pristine upstream copy and the re-applied
patches as separate commits, so the unmodified upstream state is something
an auditor can check out rather than reconstruct by subtracting a ledger
from a merged tree.
It landed as two commits split by package, not one. The point stands
either way — neither isolates an unmodified upstream tree — but a
checkable claim that is wrong costs the reader's trust in the rest of
the table.
@TheGreatAxios
TheGreatAxios merged commit 00f81b6 into main Aug 9, 2026
2 checks passed
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.

1 participant