All notable changes to this project will be documented in this file. See standard-version for commit guidelines.
2.0.1 (2023-08-23)
2.0.0 (2023-08-23)
- Dropped support for Node 12.x and 14.x
- updated all dependencies, migrated to latest major oclif version (f530ae3)
1.3.4 (2023-07-11)
1.3.3 (2023-06-27)
1.3.2 (2022-11-11)
1.3.1 (2022-08-23)
1.3.0 (2022-08-23)
- loadConfigFromPath: make configRoot a required argument to avoid edge cases (3330b4b)
1.2.1 (2022-01-15)
1.2.0 (2021-09-24)
- options: added options.typesPath to allow customizing the output path for the auto-generated typescript declaration file (80c5695)
1.1.7 (2021-08-11)
1.1.6 (2021-06-09)
1.1.5 (2021-05-31)
1.1.4 (2021-05-09)
1.1.3 (2021-05-09)
1.1.2 (2021-02-19)
- package.json: check for existence of .husky folder instead of husky command (5e4bb09)
- package.json: fixed json lint error (533d294)
- postinstall: allow git hooks installation to fail when installing the package as a dependency (2f6a973)
- postinstall: try different bash syntax for one-liner if/else when installing husky hooks (b9d2093)
- moved ramda from devDependencies to dependencies (ef9a3ba)
1.1.1 (2021-02-11)
1.1.0 (2021-01-26)
- base-config: allow defining an optional base-config (6a709b7)
1.0.0 (2021-01-12)
0.2.56 (2021-01-12)
0.2.55 (2021-01-12)
0.2.54 (2021-01-12)
- check-encryption: allow passing multiple config file arguments (42c1fad)
- core: improved error message when passing invalid options to strong-config (0bed908)
- validate: allow passing multiple config file arguments (81d0578)
0.2.53 (2021-01-08)
- check-encryption: allow passing multiple config file arguments (0c4967c)
- validate: allow passing multiple config file arguments (fba3501)
0.2.52 (2020-12-29)
- check-encryption: improve 'strong-config check' to also detect deeply nested secrets (711c7e7)
0.2.51 (2020-12-29)
0.2.50 (2020-09-14)
0.2.49 (2020-09-03)
0.2.48 (2020-07-30)
0.2.47 (2020-07-30)
0.2.46 (2020-07-30)
0.2.45 (2020-07-29)
- validate: display better error messages on validation errors (1e89a03)
0.2.44 (2020-07-29)
- options: make type-generation option a simple boolean option (9d0626b)
- validate: allow ‘validate’ cli command to operate on either ONE or ALL config files (was previously just possible for one file at a time) (514303f)
- checkEncryption: fixed overly cautious CLI ‘check’ command that would fail for a config file that didn’t even contain any secrets (15f3c3f)
0.2.43 (2020-07-22)
0.2.42 (2020-07-10)
- options: removed ‘substitionPattern’ from options (3021725)
- stricter env var substitution checks and tests (8cfa45f)
0.2.41 (2020-06-26)
0.2.40 (2020-06-25)
0.2.39 (2020-06-25)
- core: check for existence of process.env.NODE_ENV in constructor (a5dfa68)
0.2.38 (2020-06-23)
0.2.37 (2020-06-23)
- removed —verbose flag from ‘check’ and ‘generate-types’ commands (2847cc4)
0.2.36 (2020-06-22)
0.2.35 (2020-06-19)
- CI: fix manifest generation (at least locally) (dd23f35)
0.2.34 (2020-06-19)
0.2.33 (2020-06-19)
- CI: also need to run tests with --coverage flag in CI to generate the necessary coverage reports for coveralls (ca77925)
- CI: fixed wrongly named ‘yarn clean’ task that broke the release job in CI (44d5760)
0.2.32 (2020-06-10)
- debug: added ‘debug’ package and some debugging output (d5e7add)
- validate: re-add accidentally deleted error to catch statement (a85a8b4)
0.2.31 (2020-06-02)
- cli: added “yarn check-encrypt” (alias: “yarn check”) command to ensure that config files are encrypted (477a04c)
- unignore example files to add new config-fixture required by tests (98405d6)
0.2.30 (2020-06-02)
- encrypt: small error handling improvements when using sops with GCP KMS as the key provider (82eed6b)
0.2.29 (2020-06-02)
- ci: manifest generation actually needs to happen POSTrelease as it depends on an up-to-date version number which is bumped in the release-step (fd3864b)
0.2.28 (2020-06-02)
- ci: include oclif manifest in files-array in package.json so it will not only be available in development mode (1a8504d)
0.2.27 (2020-06-02)
- ci: also commit oclif.manifest.json during auto-release process (10e06b4)
0.2.26 (2020-06-02)
0.2.25 (2020-06-02)
- setup: added postinstall.js to files-array in package.json to include it in the production build of the package (33a6250)
0.2.24 (2020-05-29)
- sops: refactor postinstall script to javascript to simplify using it in the same way everywhere (e.g. local dev, from another package, in CI..) (a2f813f)
- sops: retain *.exe file extension when downloading sops on windows systems (4389fc4)
0.2.20 (2020-05-28)
0.2.15 (2020-05-27)
- sops: also search in local directory for ‘sops’ binary if it isn’t found in global $PATH (692a236)
- sops: improved error handling when sops gets a permission-denied error (ea5780c)
- security: fixed vulnerabilities in devDependencies (bebcedc)
- use async versions of ‘fs’ functions to not freeze CLI spinners when running sops-install script (73a24ae)
0.2.8 (2020-05-25)
0.2.7 (2020-05-25)
- sops: also search in local directory for ‘sops’ binary if it isn’t found in global $PATH (692a236)
0.2.6 (2020-05-20)
0.2.5 (2020-05-20)
- added postinstall script for automatically installing the needed ‘sops’ binary (652e2ea)
0.2.4 (2020-05-19)
- fixed missing typescript declarations (21fa006)
0.2.3 (2020-05-19)
- CLI: new 'strong-config generate-types' command (b5d93d8)
- options: fixed incorrect json schema for 'types' option (97b1e40)
0.2.2 (2020-03-14)
0.2.1 (2020-02-19)
- DX: improved error message when process.env.NODE_ENV is undefined (ca27d16)
- options: renamed options.types.filePath to options.types.fileName to clarify that you should not pass a full path here (because the path always defaults to options.configRoot to keep the options simple) (ba21ca7)
- schema validation: support json-schema option ‘additionalProperties: false’ to allow stricter schema validations (f79b798)
- test: fixed broken test resulting from deleting process.env.NODE_ENV and not properly restoring it after the test (ef0e084)
0.2.0 (2020-02-14)
-
schema: schema-path is now hardcoded to
${options.configRoot}/schema.json and can no longer be customized Before this commit we allowed passing a custom schema path via options.schemaPath that allowed placing the schema in arbitrary locations. While this did provide a little more flexibility, it also required extra code and added complexity. In the name of KISS we are now always defaulting the schema path to $ {options.configRoot}/schema.json, which we feel is a sane default and should satisfy the vast majority (if not all) use cases.
- schema: simplify schema handling (b04dad9)
0.1.9 (2020-01-11)
- validation: make schema validation disabled per default and explicit opt-in (d7d3b19)
0.1.8 (2020-01-07)
- add CLI with encrypt and decrypt commands (53559d6)
- --verbose flag properly working for decrypt/encrypt CLI commands (7049f5b)
- encrypt: remove parsing of verbosity level and handle as normal boolean (b03f96c)
0.1.7 (2019-11-27)
0.1.6 (2019-11-20)
0.1.5 (2019-11-19)
- example project: add dev:encrypt and dev:decrypt (c6255cb)
0.1.4 (2019-11-18)
0.1.3 (2019-11-11)
- set runtimeEnv and dev script terminal output (9727284)
- store and validate parameters object that configures strong-config internally (094de8f)
0.1.2 (2019-10-15)
0.1.1 (2019-10-14)
0.1.0 (2019-10-11)
-
The exported class StrongConfig must be instantiated to access load() and validate(). Both functions are not top-level exports anymore
-
export a class instead of two functions (4c38caf)
0.0.5 (2019-10-09)
- implement and expose validate (5639e39)
- initial setup of typescript project with tsconfig, prettier and (9273e4d)
- migrate existing strong-config (2073f91)