Skip to content
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

Jump to bottom

Update to Kotlin 2.0.20 #1474

Merged
merged 1 commit into from
Sep 1, 2024
Merged

Update to Kotlin 2.0.20 #1474

merged 1 commit into from
Sep 1, 2024

Conversation

3flex
Copy link
Contributor

@3flex 3flex commented Sep 1, 2024

Changes

  • Update Kotlin to 2.0.20
  • Update KSP to 2.0.20-1.0.24

Closes #1437

Issues

@jellyfin-bot jellyfin-bot added this to the v2.7.0 milestone Sep 1, 2024
Maxr1998
Maxr1998 approved these changes Sep 1, 2024
View reviewed changes
Copy link
Member

@Maxr1998 Maxr1998 left a comment

Choose a reason for hiding this comment

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

I suppose we could've bumped the renovate PR but this is ok too.

@Maxr1998 Maxr1998 enabled auto-merge (squash) September 1, 2024 12:10
@Maxr1998 Maxr1998 merged commit 72513e5 into jellyfin:master Sep 1, 2024
7 checks passed
@3flex 3flex deleted the kotlin-2.0.20 branch September 1, 2024 12:27
@3flex
Copy link
Contributor Author

3flex commented Sep 1, 2024

could've bumped the renovate PR

Agree, and I considered it, but there are several renovate PRs that have been open for a while so I wasn't sure it would get attention.

Have you considered auto merging renovate PRs that are just point releases? It should reduce your workload a bit.

@Maxr1998
Copy link
Member

Maxr1998 commented Sep 1, 2024

Agree, and I considered it, but there are several renovate PRs that have been open for a while so I wasn't sure it would get attention.

Fair, I'm still a bit busy with (uni) life, but it should get better soon.

Have you considered auto merging renovate PRs that are just point releases? It should reduce your workload a bit.

Not really, I usually want to follow what's changed, and quite a few dependencies don't follow semantic versioning properly. But we can definitely consider it if it stays an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Maxr1998 Maxr1998 Maxr1998 approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v2.7.0
Development

Successfully merging this pull request may close these issues.
3 participants
@3flex @Maxr1998 @jellyfin-bot