Fixed #1 - Fixed the whatsnew-** script for loading release notes into builds
Added test to ensure that release notes are parsed properly Updated to latest dependencies to fix security vulnerability Updated GH Actions Workflow to run test before updating tag Updated README.md to reflect proper whatsnew documentation.
This commit is contained in:
4
node_modules/jest-config/build/resolveConfigPath.js
generated
vendored
4
node_modules/jest-config/build/resolveConfigPath.js
generated
vendored
@@ -115,7 +115,5 @@ const makeResolutionErrorMessage = (initialPath, cwd) =>
|
||||
`cwd: "${cwd}"\n` +
|
||||
'Config paths must be specified by either a direct path to a config\n' +
|
||||
'file, or a path to a directory. If directory is given, Jest will try to\n' +
|
||||
`traverse directory tree up, until it finds either "${
|
||||
_constants.JEST_CONFIG
|
||||
}" or\n` +
|
||||
`traverse directory tree up, until it finds either "${_constants.JEST_CONFIG}" or\n` +
|
||||
`"${_constants.PACKAGE_JSON}".`;
|
||||
|
||||
Reference in New Issue
Block a user