Repository navigation
Bump README copyright range to 2026 - #964
Merged
Merged
Conversation
The copyright line still showed `2022-2025`; we're in 2026 now.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the project’s README license header to reflect the current year (2026), keeping repository metadata consistent and up to date.
Changes:
- Updated the README copyright range from
2022-2025to2022-2026.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
⏱️ Benchmark run finished in 1m 9s 📈 Compared against baseline: 20s 🚨 This PR drastically worsens generation time. 📅 Last benchmark: 2026-04-22 11:25:39 UTC You can retrigger the benchmark by commenting |
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.
The copyright line still showed
2022-2025; we're in 2026 now.