Use current year in license

[aspfohl]

What does this PR do?

mosaicml/llm-foundry#835

What issue(s) does this change relate to?

Before submitting

• Have you read the contributor guidelines?
• Is this change a documentation change or typo fix? If so, skip the rest of this checklist.
• Was this change discussed/approved in a GitHub issue first? It is much more likely to be merged if so.
• Did you update any related docs and document your change?
• Did you update any related tests and add any new tests related to your change? (see testing)
• Did you run the tests locally to make sure they pass?
• Did you run pre-commit on your change? (see the pre-commit section of prerequisites)

[hanlint]

Is it neccessary to keep licenses up to date to the year? I see many stale years in the tensorflow and torch repositories. I feel this introduces unneccessary commit / change noise -- all our files will have their last change preview in github reset.

[aspfohl]

Is it neccessary to keep licenses up to date to the year? I see many stale years in the tensorflow and torch repositories. I feel this introduces unneccessary commit / change noise -- all our files will have their last change preview in github reset.

Yea this is fair.. Originally added because I was getting linting errors when using the most up to date year, was slightly annoying to have to arbitrarily set it to 2022 🙃

It's probably worth looking into if there's other libraries that do this successfully.. ideally there would be a setting on the license checking library that allows out of date years (doesnt change all the files) but uses the most current year to generate new files. Going to close for now and reopen if theres time or I run across a better solution 😛