Skip to content

Prepare releases in 2025 #2187

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.

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
Jan 6, 2025
Merged

Prepare releases in 2025 #2187

merged 1 commit into from
Jan 6, 2025

Conversation

afranken
Copy link
Member

@afranken afranken commented Jan 6, 2025

Description

The "license-maven-plugin" configuration expects all changed files to have a copyright ending the year they are modified. A maven release updates all POMs, we need to update the copyright at the start of every year...

Related Issue

N/A

Tasks

  • I have signed the CLA.
  • I have written tests and verified that they fail without my change.

The "license-maven-plugin" configuration expects all changed files to
have a copyright ending the year they are modified.
A maven release updates all POMs, we need to update the copyright at
the start of every year...
@afranken afranken self-assigned this Jan 6, 2025
@afranken afranken merged commit 0e53139 into main Jan 6, 2025
6 checks passed
@afranken afranken deleted the prepare-2025-releases branch January 6, 2025 12:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant