meta(license): Bump copyright year #3029
Merged
Conversation
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
The copyright year should be 2024, not 2018. Would be nice if we could automate the updating of the copyright year somehow.
|
Wait to merge until we obtain approval from legal |
Co-authored-by: Chad Whitacre <[email protected]>
chadwhitacre
approved these changes
Apr 29, 2024
antonpirker
approved these changes
Apr 30, 2024
AbhiPrasad
added a commit
to getsentry/sentry-javascript
that referenced
this pull request
May 21, 2024
In getsentry/sentry-python#3029 it was raised that we need to make sure the SDK MIT License has an up-to-date year. We also need to make it a range. In this PR I went ahead and updated the dates accordingly, changed the license to directly reference `Functional Software, Inc. dba Sentry`, and re-aligned all the Licenses of individual packages to have the same format and structure.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The copyright year should be 2024, not 2018. Would be nice if we could automate the updating of the copyright year somehow.