feat(datasource/unity3d): Use Unity Releases API #33240
Open
Conversation
This file contains 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
viceice
requested changes
Dec 22, 2024
|
@viceice apparently there is nothing pending, can you merge now? Thanks! |
auto-merge was automatically disabled
January 26, 2025 12:55
Head branch was pushed to by a user without write access
|
Also, you can remove the |
rarkins
previously approved these changes
Jan 27, 2025
viceice
reviewed
Jan 27, 2025
Co-authored-by: Michael Kriese <[email protected]>
|
All comments answered and all the changes you requested are done @viceice |
rarkins
added
the
auto:no-done-comments
|
Hi there, You are using Good luck, The Renovate team |
Done! Ready to merge |
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.
Changes
The API has been changed to use the new Unity Releases API instead of the "old RSS system".
The new API is richer in metadata, allows more granularity by having queries (number of results, stream, os, architecture, version, ...). Example: https://services.api.unity.com/unity/editor/release/v1/releases?stream=LTS&platform=WINDOWS&architecture=X86_64
I have removed many tests that no longer make sense and were there before because of the inconsistencies of the RSS system. This new API has filters and these inconsistencies no longer occur.
I have also aligned the Unity terminology of streams (lts, tech, alpha, beta).
Context
Unity Releases API: https://services.docs.unity.com/release/v1/#tag/Release/operation/getUnityReleases
Example call: https://services.api.unity.com/unity/editor/release/v1/releases?stream=LTS
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: