Releases: somewhatabstract/checksync
v7.0.1
v7.0.0
Major Changes
- 6ed7f08: This fixes an issue where default argument values would override explicit configuration. This was unintentional; only explicitly provided argument values should override configuration. Since some folks may be relying on this broken behaviour, this is a major update. As part of this fix, argument parsing is now handled by yargs instead of minimist
v6.0.2
v6.0.1
v6.0.0
Major Changes
-
3b4b35d: - Node 20 or higher required. Support for Node 16 and Node 18 is deprecated.
- Eslint updated to version 9. For maintainers of this repo, this means some rules aren't working properly as they don't yet support the new flat configuration format of Eslint 9. See the configuration file for details.
- Babel, jest, typescript, and various other dependencies have been updated to their latest versions.
- Security vulnerabilities have been addressed with resolutions (https://github.com/somewhatabstract/checksync/security/dependabot/17, https://github.com/somewhatabstract/checksync/security/dependabot/18)
v5.0.5
v5.0.4
v5.0.3
v5.0.2
v5.0.1
Note: There is no v5.0.0. v5 of Checksync uses a new automated publishing setup and that didn't work for the v5.0.0 release. The changes that were in v5.0.0 have been listed below with the v5.0.1 changes.
Major Changes
-
6b561be: Migrate to TypeScript
Although there are no functional changes here, we are bumping the major version since changing our static types are provided from Flow to TypeScript could break some folks development setups.
-
14bbc5f: Working directory updates
- The location of the configuration file is now used as the current working directory, if a configuration file is used. This means that globs are resolved relative to the configuration file, not the current working directory of the process launching checksync, which makes for a more deterministic behavior for
folks trying to define and use their config files. - A
--cwd
argument has been added for specifying the working directory in cases where a configuration file is not used, or the configuration file discover needs to start in a place other than where checksync is invoked. If a configuration file is loaded, the location of that file takes precedence.
- The location of the configuration file is now used as the current working directory, if a configuration file is used. This means that globs are resolved relative to the configuration file, not the current working directory of the process launching checksync, which makes for a more deterministic behavior for
-
95d1a29: Update gitignore support to support full range of syntax. We now use the
ignore
package to support the gitignore file syntax. New verbose logging has been added to help debug ignore file issues, too.