-
Notifications
You must be signed in to change notification settings - Fork 396
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
CI maintenance because of deprecations on Oct 15 and Nov 30 2024 #2685
Conversation
checkout v3 uses node16 which reaches EOL on 15th of Oct 2024 https://github.blog/changelog/2024-09-25-end-of-life-for-actions-node16/
Gradle v2 uses node16 which will be EOL soon. "The only major breaking change from gradle-build-action@v2.12.0 is the update to require a Node 20 runtime environment. Aside from that change, this release should generally serve as a drop-in replacement for gradle-build-action@v2." Gradle updated the action name, following the advice from https://github.com/gradle/gradle-build-action/releases/tag/v3.0.0
It includes caching improvements as described here: https://github.com/gradle/actions/releases/tag/v4.0.0 windows-2022 includes node20 per https://github.com/actions/runner-images/blob/main/images/windows/Windows2022-Readme.md#nodejs
Just a node20 update per https://github.com/actions/cache/releases/tag/v4.0.0
v4 included breaking changes, but the setup here was compatible thanks to the usage of `${{ github.job }}`. https://github.com/actions/upload-artifact/releases/tag/v4.0.0 v3 artifact actions will be deprecated on November 30th https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/ node16 actions will be EOL on October 15th https://github.blog/changelog/2024-09-25-end-of-life-for-actions-node16/ These seem contradictory but I _guess_ on self-hosted runners one can keep using v3 artifact actions until November 30th.
thanks a lot! That nicely goes hand-in-hand with my current efforts to upgrade Gradle version, Target SDK version, some used libraries etc. |
There seems to be some validation issues, sorry about those. I'll try to debug them in a private fork where CI runs wouldn't need maintainer approval. Are your current efforts available in a branch? |
v3 is node20 and doesn't do validation by default like v4 validation can be disabled in v4 but when that bump is made it's probably better to resolve the issues rather than ignore them.
I pushed a few more commits, validation is no longer an issue. The issue seems to be that the dependencies logs
One dependency that was previously on jCenter was available from GitHub so that's updated in 65092dc |
Hi @anttiharju sorry for the late response. I haven't pushed my changes yet because I wasn't able to build the app with the updated libraries yet. I got stuck on in issue with the Xamarin bindings library for the new dropbox API which now includes an .aar which I wasn't yet able to bind. I only have some time again today, hopefully I will be successful later. Regarding OneDrive: In my local branch I removed these old libraries. I have implemented OneDrive using a more recent SDK a while ago, but kept the old API for users who already used it. But now it's been around for so long that I think I can safely remove it. I'll hopefully push my changes later! |
fyi: I have merged this into #2692. After some further smaller changes, the build succeeded there now! |
I'll close this here and merge the changes as part of #2692 |
thanks for all the work! |
What
I made small careful commits and tried to explain each in their message. Reviewing this PR commit-by-commit might be the easiest way to understand it.
Why
https://github.blog/changelog/label/actions+deprecation/ is a good resource for staying up-to-date on action deprecations. There are a few that would affect this repo, so I went ahead and updated the build workflow.
End of life for Actions Node16
Deprecation notice: v3 of the artifact actions
I like this app quite a bit, hopefully this PR is helpful. Thanks for all the work so far.