Skip to content

chore: update copyright year to 2026#1433

Open
rejected-l wants to merge 2 commits into
axelarnetwork:mainfrom
rejected-l:chore/update-copyright-2026
Open

chore: update copyright year to 2026#1433
rejected-l wants to merge 2 commits into
axelarnetwork:mainfrom
rejected-l:chore/update-copyright-2026

Conversation

@rejected-l

@rejected-l rejected-l commented Jan 2, 2026

Copy link
Copy Markdown

New Year Update!

This PR updates the copyright year from 2025 to 2026 in the license files.

Happy coding in 2026!


Note

Low Risk
Low risk: documentation-only change to the LICENSE header with no impact on runtime behavior or security.

Overview
Updates the LICENSE header to change the Axelar Foundation copyright year from 2025 to 2026.

Written by Cursor Bugbot for commit 5ac0d60. This will update automatically on new commits. Configure here.

@vercel

vercel Bot commented Jan 2, 2026

Copy link
Copy Markdown

@rejected-l is attempting to deploy a commit to the Axelar Network Team on Vercel.

A member of the Team first needs to authorize it.

@greptile-apps

greptile-apps Bot commented Jan 2, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Updated the copyright year in the LICENSE file from 2025 to 2026 for the new year.

  • Changed copyright year in MIT License from 2025 to 2026
  • No other copyright references in the repository needed updating

Confidence Score: 5/5

  • This PR is completely safe to merge with no risk
  • Simple one-line change updating copyright year in LICENSE file - no functional code changes, no security implications, and the update is appropriate
  • No files require special attention

Important Files Changed

Filename Overview
LICENSE Updated copyright year from 2025 to 2026 in MIT License

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Repo as axelar-docs Repository
    participant License as LICENSE File
    
    Dev->>License: Update copyright year
    License-->>License: Change "Copyright (c) 2025" to "Copyright (c) 2026"
    Dev->>Repo: Commit changes
    Note over Repo: New Year maintenance update
Loading

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.

2 participants