Releases: robertpsoane/ducker
v0.1.5
v0.1.4
v0.1.3
v0.1.2
Other
- (deps) bump bollard from 0.16.1 to 0.17.1 (#80)
- (deps) bump serde from 1.0.208 to 1.0.209 (#86)
- (deps) bump ratatui from 0.28.0 to 0.28.1 (#88)
- (deps) bump serde_yml from 0.0.11 to 0.0.12 (#87)
- (deps) bump tokio from 1.39.2 to 1.39.3 (#82)
- (deps) bump serde from 1.0.207 to 1.0.208 (#83)
- (deps) bump ureq from 2.10.0 to 2.10.1 (#81)
- (deps) bump clap from 4.5.15 to 4.5.16 (#79)
- update instructions for Arch Linux (#74)
- fix typo in README.md (#75)
v0.1.1
v0.1.0
Over the past few weeks I've had little time to add to Ducker, however I've been trying to keep on top of dependencies. I've decided to bump to v0.1.0 as Ducker's approaching a near-stable point, and to allow the semver to determine between feature update & changes and dependency patches.
Other
- (deps) bump ratatui to 0.28.0 (#70)
- (deps) bump crossterm from 0.27.0 to 0.28.1 (#62)
- (deps) bump clap from 4.5.11 to 4.5.13 (#63)
- (deps) bump tui-big-text from 0.5.2 to 0.5.3 (#64)
- (deps) bump tui-big-text from 0.4.5 to 0.5.2 (#60)
- (deps) bump tokio from 1.38.1 to 1.39.2 (#58)
- (deps) bump clap from 4.5.9 to 4.5.11 (#57)
- (deps) bump serde_yml from 0.0.10 to 0.0.11 (#53)
- (deps) bump ratatui-macros from 0.4.2 to 0.4.3 (#54)
- (deps) bump tokio from 1.38.0 to 1.38.1 (#55)
v0.0.7
Added
- (tracing) add initial tracing to ~/.local/share/ducker/ducker.log (#49)
- initial network page (#47)
- add support for listing volumes (#44)
Other
- (config) use arc instead of box for config (#52)
- (deps) bump clap from 4.5.8 to 4.5.9 (#51)
- (versions) use ureq instead of reqwest for version checks (#48)
- symlink demo.gif to fix old cargo docs
- (readme) add a note about using
--lockedto cargo installs - add an ai generated image of a duck riding a whale (#45)
v0.0.6
Over the past few days I have added a few small features, as well as bumping some dependency versions where there have been known vulnerabilities.
One of the new features is a visual prompt that there is a new version. This makes one network request at the beginning of each ducker session, but can be switched off in the config. The bottom right of the screen shows the current version, and when there is a new version, it will show both. I hope this is minimally intrusive, and am open to feedback.
The other main feature is the option to choose which command to exec into the shell as. I'm not entirely happy with how it's presented to the user and once I've got modals sorted I will probably change this up a bit. Similarly I'm wondering if its worth having two exec actions, one to use the default and one to offer the pop-up?
I have been giving versioning a bit of thought; when I started this I thought I'd start with v0.0.1 to signify the lack of completeness. I intend to add initial support for volumes and networks, as well as get some unit test coverage (so I have some degree of trust in the stability of the system!) before bumping to v0.1.0.
Added
- option to display all logs
- initial optional exec command
- add version info to bottom right of screen
Other
- start using macros for layouts
- update to issues roadmap
- (deps) bump zerovec from 0.10.2 to 0.10.4
- (deps) bump serde from 1.0.203 to 1.0.204
- (deps) bump async-trait from 0.1.80 to 0.1.81
v0.0.5
When consolidating the command field to use a common text input widget as part of the plan to add more user options, I came across a regression in exec; in essence the exec action fails, which isn't ideal.
This was introduced as part of the changes to the transition payloads. Unfortunately I'm not yet at a point where there is a test suite for the project (see the pinned issue for some wider context as to how this project got to where it is) - I think this highlights that that needs prioritising.
Fixed
- fix!(attach): exec regression fixed
Other
- use new text input widget
- add brew commands (#32)
- add CONTRIBUTING.md
- fix cargo.toml to include license from correct source