The flatpaks from CI aren't very usable in the first place, but also
take longer to complete than regular builds, as well as contribute to
our concurrent job limit. Dropping ARM builds shouldn't have much
impact, but this can obviously be reversed if people want it
Signed-off-by: Seth Flynn <getchoo@tuta.io>
These are being dropped by Nixpkgs itself soon in the near future, with
few users (on top of reduced usage of our flake/cache). We also already
have coverage for macOS builds through the aarch64-darwin target, so
this doesn't have a big impact on our end either
Obviously can be reverted if enough people want it
Signed-off-by: Seth Flynn <getchoo@tuta.io>
introduced here https://github.com/PrismLauncher/PrismLauncher/pull/3260fixes#4415
reason: some snapshot have Pre-Release in our meta but when searching in
Modrinth this needs to be translated to -pre and the reverse needed to
be done for filtering after we fetched the version.
Now there are snapshots with -pre in name and that works with Modrinth
but when we translate it back we replace it with Pre-Release so the
easeiest patch is just to double the version(one with -pre one with
Pre-Release)
The correct one would be to complicate the code and identify the
versions that need the transition and only apply this for those.
Signed-off-by: Trial97 <alexandru.tripon97@gmail.com>
As it turns out, LLDB can load Windows crash dumps!
This allows us go back to the regular (better supported) DWARF debuginfo
format used by MinGW, as now we have a tool that can both parse those
symbols *and* Windows' crash dumps. The biggest advantage here is that
once again, MinGW crash dumps can be easily inspected on Linux
Signed-off-by: Seth Flynn <getchoo@tuta.io>
Since we've started using ninja's multi-config generator, evaluating
CMAKE_BUILD_TYPE at configure-time is no longer reliable. Thankfully,
CMake offers "generator expressions" that are evaluated during build
system generation, which allows us to continue using these conditional
flags without much headache
Signed-off-by: Seth Flynn <getchoo@tuta.io>
fixes#4547
introduced by #3828
made a mistake to use addonId instead ov fileId
this only applies to modrinth
on curseforge I could not reproduce this bug
Signed-off-by: Trial97 <alexandru.tripon97@gmail.com>
fixes#4537
This ensures that when looking to uninstall a resource prism will
consider the disabled ones to.
Right now we have a guard in place to prevent resources using the same
name so this check will allways match with the correct resouce.
Signed-off-by: Trial97 <alexandru.tripon97@gmail.com>
fixes#4541
introduced in
https://github.com/PrismLauncher/PrismLauncher/commit/3c46d8a412956a759f61ae802c540ef72d00b35d
The original commit introduced m_name but never used it.
When the endActivity would be called with a count of 0 this would crash
the laucnher.
How to reproduce: try to switch your skin in quick succession until you
get 429 too many requests as response to the login.
I will also presume this is not the only crash caused by this(hopefully
it is as it was not catched for four years)
Signed-off-by: Trial97 <alexandru.tripon97@gmail.com>
Alexandru Ionut Tripon
Seth Flynn
DioEgizio
Octol1ttle
Blake Batson
timoreo
Rachel Powers
github-actions[bot]
Tayou