Skip to content

chore: update copyright year to 2025 #75

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 9, 2025
Merged

chore: update copyright year to 2025 #75

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,4 +78,4 @@ Like this project? Follow the repository on [GitHub](https://github.com/tedilabs

Provided under the terms of the [Apache License](LICENSE).

Copyright © 2021-2023, [Byungjin Park](https://www.posquit0.com).
Copyright © 2021-2025, [Byungjin Park](https://www.posquit0.com).
Copy link

Choose a reason for hiding this comment

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

medium

To improve maintainability and prevent the need for manual updates in the future, consider automating the update of the copyright year. Hardcoding the year means it will eventually become outdated again. A common approach is to use a placeholder which is then replaced with the current year by a script in your CI/CD pipeline during the build or release process.

Suggested change
Copyright © 2021-2025, [Byungjin Park](https://www.posquit0.com).
Copyright © 2021-{{ CURRENT_YEAR }}, [Byungjin Park](https://www.posquit0.com).