Remove YEAR in generated files, adhering to the community convention.#307
Merged
Conversation
Signed-off-by: Saketh Kalaga <saketh.kalaga@sap.com>
unmarshall
approved these changes
Jan 7, 2026
sanjaychatterjee
approved these changes
Jan 7, 2026
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
3 participants
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.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Generated files typically do not have the
YEARspecified in their license headers. This is to avoid seeing diffs in generated files every time the new year starts. #300 was raised to update the year but ideally we'd not want to update every year.https://github.com/kubernetes/kubernetes also does not add the year in the license header of generated files. We are following that convention now on.
This PR also fixes the broken CI due to the year diff.
Which issue(s) this PR fixes:
Fixes the CI.
Special notes for your reviewer:
cc @unmarshall
cc @kangclzjc thanks for #300 initially.
Does this PR introduce a API change?
Additional documentation e.g., enhancement proposals, usage docs, etc.: