Skip to content

Add explicit license and repository metadata for project distribution - #18

Merged
JS-banana merged 2 commits into
mainfrom
dev
Apr 20, 2026
Merged

Add explicit license and repository metadata for project distribution#18
JS-banana merged 2 commits into
mainfrom
dev

Conversation

@JS-banana

Copy link
Copy Markdown
Owner

Supplement the repo with a standard MIT LICENSE file and align Node and Rust package metadata with the maintainer's public GitHub identity and canonical repository URL.

Constraint: Keep the change limited to distribution metadata and ownership declarations
Rejected: Leave repository information only in README | package tooling would not surface it consistently
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep LICENSE ownership, package author fields, and canonical repository URL aligned across ecosystems
Tested: Parsed package.json metadata; inspected LICENSE and Cargo.toml fields
Not-tested: Application build, runtime, or packaging flows

Supplement the repo with a standard MIT LICENSE file and align
Node and Rust package metadata with the maintainer's public GitHub
identity and canonical repository URL.

Constraint: Keep the change limited to distribution metadata and ownership declarations
Rejected: Leave repository information only in README | package tooling would not surface it consistently
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep LICENSE ownership, package author fields, and canonical repository URL aligned across ecosystems
Tested: Parsed package.json metadata; inspected LICENSE and Cargo.toml fields
Not-tested: Application build, runtime, or packaging flows
Merge main into dev so the license metadata PR can land without
manual GitHub conflict resolution. Preserve main's current package
version while keeping the newly added MIT and repository metadata.

Constraint: main already advanced through release and compatibility commits after the PR branch point
Rejected: Open a replacement PR from a fresh branch | the existing PR target and history are already correct
Confidence: high
Scope-risk: moderate
Reversibility: clean
Directive: When editing package metadata on dev, re-sync against main release version bumps before opening the PR
Tested: Resolved merge conflict in package.json; parsed package.json after merge resolution
Not-tested: Application build, test suite, or runtime flows
@JS-banana
JS-banana merged commit c14c796 into main Apr 20, 2026
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