Instead of fetching the CurseForge API key from PolyMC's server, fetch
it from the files of the CurseForge app, mirrored by archive.org. We can
do this without downloading the entire 100MiB+ application by
range-requesting the specific DEFLATE block where the key is and
decompressing just that block.
Upstream changelog: https://github.com/PrismLauncher/PrismLauncher/releases/tag/8.0
(Imcomplete) list of changes in 8.0 relevant to PollyMC:
- Prism has dropped support for Mojang accounts
- https://github.com/PrismLauncher/PrismLauncher/pull/1656
- Added it back to PollyMC primarily since the Mojang authentication
code is also used for authlib-injector accounts. Some users may also
still want to be able to log in to Mojang accounts for some reason:
https://github.com/fn2006/PollyMC/issues/115#issuecomment-1805384658,
even if they do not provide authentication to multiplayer servers.
- To my surprise, I could still log in to a Mojang account, get its
skin, and launch the game. Authentication to servers, of course, did
not work.
- Tested: logging into authlib-injector, Mojang, and MSA accounts and
launching the game.
- Prism has added a built-in updater for Windows and Linux that I assume
provides similar functionality to Sparkle on macOS:
https://github.com/PrismLauncher/PrismLauncher/pull/1268. There is a
Launcher_UPDATER_GITHUB_REPO variable in CMakeLists.txt that specifies
the repo checked by the updater. I have changed this to the PollyMC
repository, and since PollyMC follows almost the same CI/release
patterns as Prism Launcher, it might work with PollyMC, too, but I
have not tested it yet.
- Add macOS support to Nix
- https://github.com/PrismLauncher/PrismLauncher/pull/1485
- Untested
- The "PollyMC-Linux-8.0.tar.gz" and similar build artifacts were
renamed to "PollyMC-Linux-8.0-Qt5.tar.gz" to match their
"PollyMC-Linux-8.0-Qt6.tar.gz" counterparts.
- Removed Windows MSVC Legacy builds
- Removed Quilt Beacon toggle, the beacon is now always disabled:
https://github.com/PrismLauncher/PrismLauncher/pull/1547,
https://github.com/PrismLauncher/meta/pull/23
- Prism removed FTB support in 7.0, but I tested creating an FTB
instance to make sure it still works in 8.0
Signed-off-by: Evan Goode <mail@evangoo.de>
We don't support that macOS version. This check also never worked, as we
never set the platform to that value.
Signed-off-by: Sefa Eyeoglu <contact@scrumplex.net>
(cherry picked from commit 0aaec9ae4f)
We don't support that macOS version. This check also never worked, as we
never set the platform to that value.
Signed-off-by: Sefa Eyeoglu <contact@scrumplex.net>
* Curseforge workarounds
This should allow people to use Curseforge without having to manually
paste a working key into the settings or change the user agent.
Signed-off-by: Lenny McLennington <lenny@sneed.church>
* chore: update cf api key api url
Sascha says the domain name we're using is not gonna be renewed, so I'm
switching it to a domain controlled by me instead so that this won't be
a problem in the future.
Signed-off-by: Lenny McLennington <lenny@sneed.church>
* feat: add ability to disable cf api key fetching
by setting the cf api key api url to a blank string
Signed-off-by: Lenny McLennington <lenny@sneed.church>
* don't ask before fetching key
* change polymc mention to pollymc
Signed-off-by: Lenny McLennington <lenny@sneed.church>
Co-authored-by: Lenny McLennington <lenny@sneed.church>
The new versioning system is based on the versioning system used by the
GNOME Foundation for the GNOME desktop.
We are dropping the "major version" as defined by SemVer and move to a
version number with a most and least significant number.
The most significant number must be incremented, if there are new
features or significant changes since last major release.
Otherwise, the least significant number must be incremented, if there
are only minor changes since the last release. New features or
significant changes mustn't be introduced by a bump of the least
significant number.
If a minor change would introduce small user-facing changes (like a
message-box or slight UI changes), it could still be classified as a
minor change.
At the end of the day, a human shall decide, if a change is minor or
significant, as there is no clear line that would separate a "minor" and
a "significant" change in a GUI-application.
Definitions:
feature: New user-facing functionality
significant change: Something that changes user-facing behavior
minor change: Something that fixes unexpected behavior
Signed-off-by: Sefa Eyeoglu <contact@scrumplex.net>
Two new build options are added:
`MAC_SPARKLE_PUB_KEY`: the public key used to verify the signatures of the appcast
`MAC_SPARKLE_APPCAST_URL`: the URL where the `appcast.xml` is located
If the updater should be disabled on macOS, set either of these to an empty string.
