Releases: zimeg/emporia-time
Releases · zimeg/emporia-time
v1.1.3
Added
- Output errors and related messages with charms logging print
Fixed
- Sign releases for mac machines without configuration errors
- Return exit codes after time command subshell measures usage
- Output flake build as shorter etime instead of project name
- Include manual pages when installing using flake derivation
- Correct spellings of documentation to match common wordings
Maintenance
- Update language linter configurations to the latest version
- Make test coverage dashboards when running coverage commands
- Exit with success if updates to dependencies were not found
- Reduce the set of permission required for the action runners
- Set action steps to a pinned version with escaped variables
- Remove flake utilities not needed for packaging this project
- Follow the unstable packages of nix with development inputs
- Store secrets in obfuscated writing among other project file
v1.1.3-rc.8
Maintenance
- Store secrets in obfuscated writing among other project file
v1.1.3-rc.7
Maintenance
- Store secrets in obfuscated writing among other project file
v1.1.3-rc.6
Maintenance
- Store secrets in obfuscated writing among other project file
v1.1.3-rc.5
Maintenance
- Store secrets in obfuscated writing among other project file
v1.1.3-rc.4
Fixed
- Sign releases for mac machines without configuration errors
v1.1.3-rc.3
Fixed
- Sign releases for mac machines without configuration errors
v1.1.3-rc.2
Fixed
- Sign releases for mac machines without configuration errors
v1.1.3-rc.1
Fixed
- Sign releases for mac machines without configuration errors
v1.1.2
Rolling builds are now released with all of the latest dependencies! And with nix
this is packaged unversioned ❄️
$ nix run github:zimeg/emporia-time# sleep 12
Help pages were improved a small amount too 📚 ✨
Added
- Package the build in a flake and test with propogated timing
Fixed
- Set the version of the latest flake builds to be unversioned
- Remove an extra percent sign from help page sureness example
Maintenance
- Write reminders for the steps involved in wiki page updates
- Wait until tests pass before merging updates to dependencies
- Find missing references that the above changes might expect
- Check that upstream merges do not let dependencies skip test
- Setup the self hosted runner on other computed configuration
- Upload test results to gather insights into possible flakes
- Run tests after each push or workflow dispatch for sureness
- Update development and release dependencies on some schedule
- Bump the go runtime version to version 1.24.1 when building
- Run release snapshots when starting with a workflow dispatch
- Update the vendor hash of go modules after updates are made
- Run tests and packaging scripts again after automatic merges
- Include the required token for starting the testing workflow
- Request updates to dependencies at a much more frequent time
- Remove deprecated options from packaging program for release