[Maintenance]: Update copyright year ranges in source files changed in 2026

[loveRhythm1990]

Is there an existing issue for this enhancement?

• I searched the existing issues and did not find a duplicate.

Problem

The repository contribution rule requires the copyright header year to be updated whenever a source file is modified in a later year:

• YYYY becomes YYYY-currentYear.
• YYYY-ZZZZ updates the ending year to currentYear.
• Only files actually changed by the PR should be updated.

PR #578 was merged in 2026 and modified the following Go source files, but their headers remained Copyright 2025 Matrix Origin:

• api/core/v1alpha1/toml_config.go
• api/core/v1alpha1/toml_config_test.go
• pkg/controllers/cnset/resource.go
• pkg/controllers/dnset/resource.go
• pkg/controllers/logset/configmap.go
• pkg/controllers/proxyset/resource.go
• test/e2e/logset_test.go

These headers should have been changed to Copyright 2025-2026 Matrix Origin as part of that PR. Some of these files have received additional 2026 changes and still retain the single-year header on main.

Expected behavior

Every source file changed in 2026 has a compliant year or year-range header, without bulk-changing unrelated files.

Suggested work

• Update the affected files when they are next modified, or address this known set in a focused maintenance PR.
• Add or adjust a lightweight check so a modified source file with an outdated ending year is reported during review.
• Ensure the license checker accepts the required year-range format.

Acceptance criteria

• The listed affected files use Copyright 2025-2026 Matrix Origin.
• Unrelated files are not bulk-updated.
• CI accepts the year-range format and detects outdated headers on newly modified source files.

References

• PR fix: make fileservice config deepcopy #578: fix: make fileservice config deepcopy #578
• Merge commit: 3de66ab
• License/check repair context: fix: fix CI checks — CRD regeneration, license config, and lint #588