chore: update copyright year range - #17
Merged
Merged
Conversation
The project began in 2024 and is still active in 2026. A range preserves the original claim rather than replacing it, which a bare swap to 2026 would have done.
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.
LICENSEstill readCopyright (c) 2024. First commit was 2024 and the project is active in 2026, so this is a range rather than a swap — replacing the year outright would drop the original claim.The READMEs carry no year (
MIT © Rohan Poudel), so nothing else needed changing.mcp/LICENSEis handled in #16, where that file lives. It gets2026alone, since the MCP package is new work rather than a continuation.