Skip to content

v0.4.0-dev.1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 04 Oct 07:36
· 39 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.4.0-dev.1
3ff9d03
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.4.0-dev.1: test build for developers

This pre-release is for the Borea team and developers who want to test v0.4.0 before it is released.
It is not for users. For normal use, stay on v0.3.2.
Tell us what did not work: Discord | GitHub issues

Please test these first

  • Pins: pin a mod from its "..." menu, then run "Update all". The pinned mod should stay, and the other mods should update. When a pin keeps another mod from its newest release, that row should say which pin holds it back.
  • Modpacks: detach a mod of a pack from its "..." menu, update the pack, and attach the mod again. The pack update should leave the detached mod alone and name it.
  • Descriptions: open mod pages with long descriptions and release notes. Links, tables, lists and code should look as the author wrote them, and a drag should select across all of it.
  • The Content tab: mods you installed by hand should show in "Not managed by Borea", and "Manage with Borea" should take one over.
  • Pins and detached mods are new in the record of an instance. An older Borea drops them when it saves such an instance, so test them in an instance you do not open with v0.3.x again.

New since v0.3.2

  • Descriptions and release notes show links, tables, dividers, nested lists and code as the author wrote them, and a drag selects text across all of it.
  • Pin a mod at its version, and see which pin holds back the update of another mod.
  • Detach a mod from its modpack and attach it again.
  • The "Manual installs" tab is gone; mods that Borea did not install show on the Content tab.
  • The "..." menu of a mod or pack page has "Copy share link" and "Report".
  • The License filter of Discover takes more than one license.
  • Mod authors: the listing editor previews the description while you type.
  • The command line has borea pin, borea unpin, borea pack detach and borea pack attach.

How to get the next test builds

With the default update channel, "Stable releases", Borea does not tell you about pre-releases like this one.
To see them, open Settings, General, and set "Update channel for Borea" to "All releases, dev builds included".
"Check for updates at start" must be on.
When v0.4.0 is released, every channel tells you about it.

Downloads

File SHA-256
Borea-0.4.0-dev.1-linux-x64.tar.gz 914cc5acdd2751a73f22908ea2e94d2d1535dc2148d66a9184e8ddcff55c5356
Borea-0.4.0-dev.1-macos-arm64.tar.gz 3d390c6c775bd7ccca68e66c7c3efb63fa9913a24bd5ac0dd7076c1c142c3386
Borea-0.4.0-dev.1-win-x64.zip e641cbf16edd7ce26ae0617645b84c0094a85894506227377e4c12f2e39068ab
Borea-0.4.0-dev.1.cdx.json f74c609afbf7ba5ec0b23f3abc09efde55885add8684dc04e300d10a71711968
Borea-Cli-0.4.0-dev.1-linux-x64.tar.gz 981c4d643eca23c5639c69dc37602fdf1bd5822d8f09e6f400e9df3452dcbd70
Borea-Cli-0.4.0-dev.1-macos-arm64.tar.gz b7f3f7fc5efbd82badce9deb3e99580fc60f885c416f7701459790164c9b1942
Borea-Cli-0.4.0-dev.1-win-x64.zip e5cfe51502f1e32a471de8c91f67acd1c788cca0a83c476c5421d5b038eb0ac5
Borea-Cli-0.4.0-dev.1.cdx.json 3092921edfe6c88494238a13d02ab2ef0007a1e629311da335183903eaf8d113

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.
Put that folder where it can stay, for example %LocalAppData%\Programs\Borea on Windows or ~/.local/share/Borea on Linux, 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.

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. Unpack and start Borea from Terminal, not from Finder: tar -xzf <file>, then run ./borea inside the new folder of the App archive for the App, or ./borea --help inside the new folder of either archive.
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.4.0-dev.1.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.4.0-dev.1.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 will come in the future and is tracked in #76.

What's Changed

Full Changelog: v0.3.2...v0.4.0-dev.1

Contributors

Maximilian-Nesslauer
Assets 12
Loading