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.

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

Restore default version support for SpaceDock #4272

Merged
merged 1 commit into from
Dec 6, 2024

Conversation

HebaruSan
Copy link
Member

Problem

BeyondJool currently has this inflation error:

No files found matching find="BeyondJool" to install!

Cause

There's a 1-MB dummy download with a version of TEST (do not use) sitting at the top of the list of releases:

The inflator is downloading this and discovering that it doesn't contain the mod, even though the "Set as default" button was used on SpaceDock to mark the previous download. This most likely broke when we added the --releases and --skip-releases options to Netkan because support for the default release flag was only in SpacedockMod.Latest, which is no longer used because it only returns one version.

Changes

Now the default release setting is used to sort the releases from SpaceDock, so it will determine which release gets inflated. If we inflate multiple releases, the others will be checked after the default.

@HebaruSan HebaruSan added Bug Something is not working as intended Easy This is easy to fix Netkan Issues affecting the netkan data labels Dec 6, 2024
@HebaruSan HebaruSan merged commit 92fe172 into KSP-CKAN:master Dec 6, 2024
3 checks passed
@HebaruSan HebaruSan deleted the fix/spacedock-default-version branch December 6, 2024 02:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is not working as intended Easy This is easy to fix Netkan Issues affecting the netkan data
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant