Repository navigation
chore(license): move generators to MIT and remove federation generator - #455
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <[email protected]>
🦋 Changeset detectedLatest commit: 8a7c2aa The changes in this PR will be included in the next version bump. This PR includes changesets to release 10 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
What This PR Does
Moves every generator in this repo from the AGPL-3.0 / commercial dual license to the MIT license (Copyright EventCatalog Ltd). The generators no longer need a license key to run. It also removes
@eventcatalog/generator-federation, because federation is now part of EventCatalog core.Changes Overview
Key Changes
LICENSE.LICENSE-OPENSOURCE.mdandLICENSE-COMMERCIAL.md.LICENSEfile to each package, so the published npm tarballs include it."license": "MIT"in every packagepackage.json(they saidISCorDual Licensebefore).shared/checkLicense.tsand the@eventcatalog/licensedependency.checkLicense()calls andEVENTCATALOG_LICENSE_KEY_*lookups from all 10 generators. The package update check stays.licenseKeyoption from the generator types and zod schemas.checkLicensemocks from the tests.packages/generator-federation,examples/generator-federation, the federation images, and the federation.gitignoreentries and README links..env-examplefiles.minorbump for all 10 generators.How It Works
Each generator called
checkLicense(pkgName, key)at startup. That call ended the process when no valid plugin key or Scale key was found. The call and its helper are gone, so the generators now go straight tocheckForPackageUpdateand then generate.Breaking Changes
None for users:
licenseKeyoption left ineventcatalog.config.jsis ignored. The asyncapi and graphql zod schemas are not strict, so the unknown key is dropped.EVENTCATALOG_LICENSE_KEY_*env vars are no longer read.Additional Notes
EVENTCATALOG_SCALE_LICENSE_KEYand the "EventCatalog Starter" notes stay in the chat examples. Those are for EventCatalog core features (chat), not for the generators.@eventcatalog/generator-federationis still on npm. You may want tonpm deprecateit and point users to core federation.pnpm run buildpasses, andCI=true pnpm run testpasses for all 10 packages.