Files
ac-qu-ai-nt/multibinary/CHANGELOG.md
release-plz-for-ac-qu-ai-nt[bot] 062c31bd9a chore: release
2024-10-06 03:34:57 +00:00

2.7 KiB

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

0.0.8 - 2024-10-06

Added

  • initialize core, gui-eframe, and tui-ratatui crates and use them in the multibinary

0.0.7 - 2024-10-05

Other

  • updated the following local packages: ac-qu-ai-nt-cli-clap

0.0.6 - 2024-10-05

Fixed

  • cover the new cases of Command for GuiEframe and TuiRatatui

Other

  • correctly add gui-eframe and tui-ratatui as features this time around
  • add gui-eframe and tui-ratatui as subcommands with aliases gui and tui respectively
  • add gui-eframe and tui-ratatui as features

0.0.5 - 2024-10-05

Other

  • [breaking] put accessing the cli under a subcommand like the README suggests it would be

0.0.4 - 2024-09-30

Added

  • (multibinary) initialize a basic tracing subscriber until this is changed to a directory one using tracing-appender at a later time
  • make tracing a crate feature and make it a default feature of the current crates

0.0.3 - 2024-09-30

Added

  • [breaking] this is the correct way to format a breaking change unlike my previous commit - ensure the application data directory, and the tracing directory within it, exists

Other

  • add tracing and tracing-subscriber as dependencies
  • reserve a data directory for the application

0.0.2 - 2024-09-25

Other

  • release

0.0.1 - 2024-09-24

Other

  • add licenses and other required metadata to the crates
  • initialize a Cargo workspace with a cli-clap and a multibinary package to align with how I want the project to work (wherein features can be turned off to optimize the resulting binary, and there are different interfaces (GUI vs TUI vs CLI vs just an API vs just a web app or any permutation of these) to choose from depending on the occasion)