Skip to content

fix: Ensure all headers in the same package have the same copyright year#8016

Open
danieljbruce wants to merge 6 commits intomainfrom
copyright-year-changes
Open

fix: Ensure all headers in the same package have the same copyright year#8016
danieljbruce wants to merge 6 commits intomainfrom
copyright-year-changes

Conversation

@danieljbruce
Copy link
Copy Markdown
Contributor

@danieljbruce danieljbruce commented Apr 10, 2026

Description

Solves issue googleapis/librarian#4753. Ensures that all headers in files of the same package have the same copyright year. Files containing no copyright year also now have a copyright year as this was a related issue discovered by the testing script.

Impact

Assists with librarian migration from https://github.com/googleapis/librarian/milestone/88.

Testing

The root directory of google-cloud-node doesn't use CI tests, but I created a check-package-years.sh script in the bin folder that only succeeds if all header files have the same copyright year for every file in a given package.

Additional information

Headers with copyright years needed to be generated for some files:

image

Some .jsdoc generation files will also generate headers for 2026 which is desirable:

image

@danieljbruce danieljbruce requested a review from a team as a code owner April 10, 2026 17:34
Copy link
Copy Markdown
Contributor

@pearigee pearigee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we skip the proto files? They are just copied artifacts from google3 and the changes may not stick.

@pearigee
Copy link
Copy Markdown
Contributor

Also, it looks like the snapshot testing in the unit tests may have broken as a result of this?

@danieljbruce
Copy link
Copy Markdown
Contributor Author

Also, it looks like the snapshot testing in the unit tests may have broken as a result of this?

Ah. Ok. This is a good catch. I thought the presubmit / units test weren't required, but the snapshots definitely should match.

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