Bump copyright date#694
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Note
Low Risk
Header-only metadata change with no impact on merge logic, security, or data handling.
Overview
Updates the Arcee AI copyright notice from 2025 to 2026 in the first-line header of Python modules under
mergekit/(architecture, io, merge methods, evo, moe, scripts, tokenizer, tokensurgeon, and related packages). TheLGPL-3.0-onlySPDX line is unchanged.There is no change to runtime behavior, APIs, or dependencies—only license header metadata.
Reviewed by Cursor Bugbot for commit 32470ce. Bugbot is set up for automated code reviews on this repo. Configure here.