Skip to content

v0.6.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 02 Nov 19:02
· 103 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.6.0
6769beb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Borea v0.6.0

Borea is the community content manager for Kitten Space Agency. It finds mods, vehicles and saves, installs them with everything they need into separate instances of the game, and starts the game through StarMap.

Website | Discord | Content index | Source and issues

Updating from v0.5.x

Click "Update now" on the Home banner, or run borea update-self.
Your instances, mods and settings stay as they are.

What's new

  • Vehicles and saves. You now find them in Discover and install them just like mods, with all the mods they need. Before you install a vehicle, you can look at it in 3D, drawn from the parts of your own KSA install.
  • Share your own creations. Pick a vehicle or a save from any of your instances, describe it, add a few pictures, and publish it on ksamods.gg. Borea finds the mods it needs and draws a cover for you, and a few minutes later every Borea player can find it in Discover.
  • Keep a game build. An instance can stay on the KSA build it was made for, so a game update no longer breaks your modded setup.
  • Choose the mod loader version per instance. Each instance can use its own StarMap version, and a missing one installs with one click.

Smaller improvements

  • "Update all" shows what it will change before it starts.
  • Vehicles in Discover have small pictures, and borea:// links open a listing straight in Borea.
  • A mod page shows which mods and vehicles need it, and which mods conflict with it.
  • The License filter groups licenses by what they allow, and you can still narrow it down to an exact license.
  • When a mod offers a smaller download for your operating system, Borea takes that one.
  • A listing whose forums thread is gone shows a warning and is no longer offered for new installs. Anything you already installed keeps working.
  • Simplified Chinese is complete, thanks to @kuxiaowo.
  • The .NET runtime inside Borea is now 10.0.14, with the latest security fixes.

Fixes

  • Scrolling with the mouse wheel over an open drop-down could freeze Borea.
  • "Update all" stopped after a few mods.
  • On Linux, a game path that differed only in upper and lower case was overwritten.

Good to know

  • A kept build is a full copy of KSA, about 2.8 GB on Windows. You find your kept builds in Settings > Game, and you can remove the ones that no instance uses.
  • When a KSA build changes the format of its part files, the 3D preview pauses until a Borea update supports the new format. Everything else keeps working.
  • Going back to v0.5.2? It does not know kept builds or the vehicles and saves that Borea installed. Those instances start on the current build again, and the vehicles and saves stay in place but are no longer managed.

For mod authors and stewards

  • A release can carry smaller archives for each operating system next to the archive for every platform. The contributing guide explains how to name them.
  • The listing editor reads releases with a tag prefix the same way the index does.
  • Stewards have a new Statistics tab.

Thank you

Sharing vehicles and saves was built together with @SafeShows, who runs ksamods.gg. Thank you for the great collaboration!

Full changelog: v0.5.2...v0.6.0

Downloads

File SHA-256
Borea-0.6.0-linux-x64.tar.gz 47432773ef9cec840736a8f3fd2f936084b0a0832ed9129d2714602a968800d8
Borea-0.6.0-macos-arm64.tar.gz 6d0ebb59cbc8493da9ce61c367f87e70c9780051750c8e50acd3411383f9d884
Borea-0.6.0-win-x64.zip f5c278ed7c48e3d2cd20a604ef3bcf6da6860c53396540e7699b3d5f71668d2b
Borea-0.6.0.cdx.json 6e2e7f78a1ae88d5c285c211c0e18f7158f3ec4b0249ef31ce8a5d4f26646567
Borea-Cli-0.6.0-linux-x64.tar.gz 5e0cf8cbe504ae2c5ce7412a511e8e2041171390e67830442d64941649e550ea
Borea-Cli-0.6.0-macos-arm64.tar.gz a10b100574d705e79b7fe506539924b2f58062cc3dd063d4d0eb6193b8c5b40b
Borea-Cli-0.6.0-win-x64.zip 93463a905d700ab5b776fe0eb60ce20a5806850639364c5b7b73a65baae000d4
Borea-Cli-0.6.0.cdx.json 8e12cbed5ee0f986032d79ae064ed970cd90b28ffba33f83f9c321b56b2db145

Each platform has two archives.
The App archive, for example Borea-<version>-win-x64.zip, contains the program borea.
Without arguments, borea opens the desktop App, and with arguments, it runs a command.
Most users want this archive.
Archives whose names start with Borea-Cli- are a smaller download that contains only the command line.

The builds include the .NET runtime and are self-contained, so there is nothing to install first.

Each archive contains borea (borea.exe on Windows), LICENSE and THIRD-PARTY-NOTICES.txt, in a folder named Borea, or Borea-Cli for the CLI archive.
The App archive also contains BRANDING.md, because the Borea logo in the App is not covered by the MIT License.
On macOS, the App archive unpacks into Borea.app instead, with the same files inside.
Put that folder where it can stay, for example %LocalAppData%\Programs\Borea on Windows, ~/.local/share/Borea on Linux or Applications on macOS, because Borea updates itself into the folder it runs from.

First start

These builds are not code signed, so the first start might take an extra step on Windows and macOS. The README has the long explanation.
Code signing policy: https://ksamodding.github.io/Borea/code-signing.html

Windows. Right-click the zip, open Properties and select Unblock.
Then unpack the App archive and start borea.exe, or run .\borea.exe --help in PowerShell in the unpacked folder of either archive.
Without that step, Windows shows "Windows protected your PC". This is because the file might not be downloaded often and is not signed. Select "More info", then "Run anyway".

Linux. Unpack the App archive and run ./borea for the App, or run ./borea --help in the unpacked folder of either archive.
After the App has started once, Borea is in the application menu and starts from there without a terminal.
Both need the ICU and OpenSSL libraries of your distribution, and only the App also needs the X11, ICE, SM and fontconfig libraries. Most desktop installs already have them. See Readme.

macOS. Double-click the App archive to unpack it, drag Borea.app into Applications and open it.
macOS says that Apple could not verify Borea. Select Done, then open System Settings, Privacy & Security, and select "Open Anyway" there.
For the command line, run /Applications/Borea.app/Contents/MacOS/borea --help, or unpack the CLI archive and run ./borea --help in the new folder.
The macOS builds are for Apple silicon. Intel Macs are not supported.

Provenance

To check that a file came from this workflow:

gh attestation verify <file> --repo KSAModding/Borea \
  --signer-workflow KSAModding/Borea/.github/workflows/release.yml

Borea-0.6.0.cdx.json is the software bill of materials for the App archives, in CycloneDX JSON.
The App contains the command line, so this list includes the NuGet packages of the App and of the CLI.
Borea-Cli-0.6.0.cdx.json is the software bill of materials for the CLI archives and includes only the packages of the CLI.
Each list includes the version, license and hash of every package.
Each list is attested only to the archives that it describes, and you can use this command to prove that it belongs to one.
With --format json, the output includes the attested list.

gh attestation verify <archive> --repo KSAModding/Borea \
  --signer-workflow KSAModding/Borea/.github/workflows/release.yml \
  --predicate-type https://cyclonedx.org/bom

Signing is prepared in #678. Until it is in place, the checksums and the attestation above are how a file is checked.
Code signing policy: https://ksamodding.github.io/Borea/code-signing.html

What's Changed

New Contributors

Full Changelog: v0.5.2...v0.6.0

Contributors

weblate, dependabot, and 4 other contributors
Assets 12
Loading