chore: relicense to MIT#12
Merged
Merged
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
1 participant
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
Relicense
@agentage/memory-corefromUNLICENSEDto MIT.LICENSE(standard MIT, "Copyright (c) 2026 Agentage Contributors").package.json:"license": "UNLICENSED"->"MIT".package.json: version0.1.0->0.1.1(see Publishing below).package-lock.json: synced rootversion/licenseto match.LICENSE.Why
Makes the package openly reusable and unblocks the MIT-licensed
@agentage/cli, which depends on this package - a permissive dependency must itself be permissively licensed.Publishing (after merge)
The publish workflow only runs on
workflow_dispatchor a release-pattern commit tomaster, and it skips any version already on npm.0.1.0is already published, so this bump to0.1.1is required for the MIT build to actually publish. Thischore:commit does not match the release pattern, so merging does not auto-publish - a maintainer triggers the release separately.Verification
npm ci && npm run verifyandnpm run test:coverageboth pass locally (49 tests, build green).