Skip to content

Remove generated notice bundles and custom tooling - #13

Merged
jacksteamdev merged 1 commit into
mainfrom
chore/remove-notice-tooling
Nov 12, 2026
Merged

jacksteamdev merged 1 commit into
mainfrom
chore/remove-notice-tooling

Conversation

@jacksteamdev

Copy link
Copy Markdown
Collaborator

Summary

- notices/ generated bundles and inventory
- tools/notices/ generator, verification and packaging
- notices CI job and build-time notice checks
+ tools/ci/versions.ts shared build-tool pins
  LICENSE and adapted Astronomy Engine MIT attribution

Worker and browser builds no longer require committed generated notices. Keep required source attribution and document that compiled redistribution still needs applicable dependency licenses and MPL source access.

Evidence

  • Before: both build wrappers call check(root) and copy generated notice bundles; removing notices/ leaves missing build inputs.
    After: browser Wasm/Vite build and TypeScript check pass with no notice directory; Worker verification build passes all 6 structural cases and 11 adapter checks in local workerd.
  • Before: CI selects jobs using notices/inventory.json and CI TypeScript configuration extends removed notice tooling.
    After: 10 CI-helper tests and standalone CI TypeScript checking pass; Cargo package inventory retains LICENSE and adapted-code attribution.

Merge Danger

Door: two-way

Revert restores the tooling and bundles. No chart calculation or fixture changes.

Blast Radius: builds

Local builds no longer assemble redistribution license bundles. Distributors must supply the licenses and source-access information for components they ship.

@jacksteamdev
jacksteamdev merged commit 689937c into main Nov 12, 2026
7 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