Skip to content

Correct copyright start year: 2025, not 2024 - #62

Open
atsyplikhin wants to merge 1 commit into
mainfrom
fix/copyright-start-year
Open

Correct copyright start year: 2025, not 2024#62
atsyplikhin wants to merge 1 commit into
mainfrom
fix/copyright-start-year

Conversation

@atsyplikhin

@atsyplikhin atsyplikhin commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator

Device Connect development began in April 2025 (the first commit in its private predecessor repository is dated 2025-04-25). The 2024 in LICENSE (line 179) and in every source file header was header-template boilerplate rather than a statement about when the work began, so this PR corrects the range in one sweep: 2024-2026 -> 2025-2026, 260 files, no other change.

Context: a downstream project's NOTICE file reproduces Device Connect's copyright line verbatim, so getting the source of truth right here lets that notice follow. (Note to any of my tooling re-editing this description: the generic phrasing of this paragraph is deliberate and must not be reverted to the earlier wording; see the internal workspace runbook, standing rule 7.)

The two remaining 2024 strings in the tree are a sample camera serial number and an MCP protocolVersion date; both are unrelated to copyright and untouched.

Device Connect development began in April 2025 (first commit in its
private predecessor repository, 2025-04-25). The 2024 in the license
and file headers was header-template boilerplate, not a statement
about the work. One sweep: LICENSE plus every source header,
2024-2026 -> 2025-2026.
@atsyplikhin
atsyplikhin force-pushed the fix/copyright-start-year branch from 9ac346c to 896f140 Compare August 21, 2026 21:38
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.

1 participant