Releases: electricduck/booski
Releases · electricduck/booski
0.3.1
🗑 Old Release
This is an old release, kept here for archival purposes. Unless you absolutely need it, see latest.
🔨 What's Fixed?
- Introduced more platforms for pre-built versions
- Linux (ARM64)
- Linux musl (x86_64, ARM64) — for distros like Alpine Linux, using musl instead of glibc
- Windows (ARM64)
- macOS (Intel, Silicon)
- macOS is entirely untested but there's no reason it shouldn't work (hooray for .NET!)
- Added support for macOS's user configuration directory
- Renamed
BOOSKI_CONFIG_PATH
envvar toBOOSKI_CONFIG_DIR
BOOSKI_CONFIG_PATH
will still work, butBOOSKI_CONFIG_DIR
will be used over it
This is a minor update; a full changelog (since the previous major update) can be seen at 0.3.
0.3
🗑 Old Release
This is an old release, kept here for archival purposes. Unless you absolutely need it, see latest.
✨ What's New?
- New CLI UX
- The main application is now ran from
booski run
. See--help
(andrun --help
) for more details. - New arguments for
run
--no-connect-<service>
to temporarily disable connecting to a service--exit-connect
for testing connections to services (and then immediately exiting before caching posts)
- The main application is now ran from
- File-based configuration
- On first startup, this will be created for you (and it's location printed)
- All arguments used for configuration (that were present in 0.2) have been removed in favour of a configuration file
- Configuration files will be stored in the same directory as the database, and should be computed automatically
- Use
BOOSKI_CONFIG_PATH=<path>
to set the configuration directory manually
- Username mapper
- This allows usernames to be automatically mapped depending on the service a post is cross-posted to
- See
booski usernames --help
for details - Currently, none of these mapped usernames are validated — be careful!
- Update notifications
- On startup, a check will be done against this repository to see if a newer version is available
- Currently, you still must manually download the new release and replace the old version. An automatic updater is a low-priority, as in practice this should be done by some sort of external package manager
- Use
BOOSKI_IGNORE_UPDATES=1
to disable this
- Various new validations for user-given values
💥 Breaking Changes
- Verbs are now used. Invoking the main application is done from
booski run
- All arguments used for configuration have been removed. These are replaced by the configuration file (
booski.json
) as follows:--username
→.Clients.Bluesky.Username
--password
→.Clients.Bluesky.Password
--host
→.Clients.Bluesky.Host
--mastodon-instance
→.Clients.Mastodon.Instance
--mastodon-token
→.Clients.Bluesky.Password
--telegram-channel
→.Clients.Telegram.Channel
--telegram-token
→.Clients.Telegram.Token
--x-api-key
→.Clients.X.ApiKey
--x-api-secret
→.Clients.X.ApiSecret
--x-access-token
→.Clients.X.AccessToken
--x-access-secret
→.Clients.X.AccessSecret
⚙️ Development
These changes are important to note if you plan on building and/or contributing to Booski
- The beginnings of Threads support can now be found around the codebase
- There is nothing concrete yet: the API itself hasn't even been implemented
- Support for Threads is low-priority and this work may never be completed
- Due to dotnet/runtime#72604, only .NET 9.0 (currently in preview) is supported. There are no plans to support .NET 8.0 (or below) as Microsoft seem entirely unwilling to fix this issue for those versions
0.2.1
0.2
🗑 Old Release
This is an old release, kept here for archival purposes. Unless you absolutely need it, see latest.
✨ What's New?
- Initial public release. Please be kind! ✨
- Currently only Windows (x64) and Linux (x64) is supported. If you absolutely need another platform, build it yourself
- There is no update checking method built into the application currently. You will need to keep an eye on this repository and update yourself
💥 Breaking Changes
(None. Hooray!)
⚙️ Development
These changes are important to note if you plan on building and/or contributing to Booski
- Due to dotnet/runtime#72604, only .NET 9.0 (currently in preview) is supported. There are no plans to support .NET 8.0 (or below) as Microsoft seem entirely unwilling to fix this issue for those versions