Releases: tinted-theming/tinty
Releases · tinted-theming/tinty
v0.22.0
v0.21.1
Fixed
- Fix bug where
tinty build
subcommand doesn't supportfilename
config.yaml property
v0.21.0
Changed
- BREAKING: MacOS breaking change only since Tinty now uses
XDG
paths
for config and data directories while falling back toXDG
defaults
for these dirs if the environment variables aren't set. This is how
Tinty functions on Linux already
v0.20.1
Fixed
- Fix bug where
tinted-builder-rust
displays build information by
default whentinty apply
is run
v0.20.0
Added
- Add
--quiet
flag forapply
,install
andupdate
subcommands - Add
sync
quality-of-life subcommand combininginstall
andupdate
subcommands
Fixed
- Fix bug where Tinty won't update after custom schemes have been built
in local templates
v0.19.0
Added
- Add
--quiet
flag forbuild
subcommand - Add
--verbose
flag forinit
subcommand
Changed
- Update dependencies
Fixed
- Fix bug where
scheme_partial_name
doesn't render correctly in all
situations when a scheme name exists in schemes and custom schemes
v0.18.0
Added
- Add
--custom-schemes
flag support fortinty info
Fixed
- Fix bug where
tinty generate-scheme
would generate schemes without
scheme values being wrapped in double quotes - Fix error message when
tinty list --custom-schemes
when no custom
schemes exist
v0.17.0
Added
- Add
tinty generate-scheme
command to generate a scheme based on
provided image input, with the included functionality of saving this
scheme file and applying it withtinty apply
. - Add
--custom-schemes
flag fortinty lint
subcommand to list custom
schemes saved withtinnty generate-scheme
.
v0.16.0
Added
- Add
theme-file-extension
option in item config to allow users to
define a custom theme extension that isn't/\.*$/
Release 0.15.0
Changed
- Remove stderr comment output for
tinty generate-completion
- Update to latest tinted-builder using newly created ribboncurls
mustache template rendering engine.