apollo-opentracing
apollo-opentracing copied to clipboard
fix: Update dependency ts-jest to v27.1.5
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| ts-jest (source) | 27.0.4 -> 27.1.5 |
Release Notes
kulshekhar/ts-jest (ts-jest)
v27.1.5
Bug Fixes
v27.1.4
Bug Fixes
- compiler: revert #3194 (#3362) (2b7dffe), closes #3272
- remove
esbuildfrom peer dependency (#3360) (8c8c1ca), closes #3346 - support Babel config file with
.cjsextension (#3361) (5e5ac4a), closes #3335
v27.1.3
Bug Fixes
v27.1.2
Bug Fixes
v27.1.1
Bug Fixes
- bring back
afterProcesshook (#3132) (2b6b86e) - make
esbuildas optional peer dependency (#3129) (20258de)
v27.1.0
Features
- allow subclasses to extend
processAsyncandgetCacheKeyAsync(#3047) (571a880) - config: support custom AST transformers written in TypeScript (#3063) (340a305), closes #2831
- export
ts-jestpublic apis fromindex.js(#3080) (53175dd), closes #3045
Code Refactoring
- utils: deprecate
mockedutil function (#3102) (55e69f1) - define clear type for
compileroption (#3087) (cc42daf) - transformers: deprecate
path-mappingAST transformer (#3088) (d8f6b96) - transformers: use ts
factoryAPI forhoistingAST transformer (#3058) (a72f51d)
DEPRECATIONS
- transformers:
path-mappingAST transformer is deprecated and will be removed in v28.0.0. One should use an alternative one like https://github.com/LeDDGroup/typescript-transform-paths instead. - utils:
mockedfunction is deprecated and will be removed in v28.0.0. The function has been integrated intojest-mockpackage as a part of Jest 27.4.0, see https://github.com/facebook/jest/pull/12089. One should use the one from Jest instead
27.0.7 (2021-10-16)
Bug Fixes
27.0.6 (2021-10-14)
Bug Fixes
27.0.5 (2021-08-14)
Bug Fixes
- cli: add migration
tsConfigoption forts-jestconfig options (#2794) (781710b), closes #2764 - cli: fix
config:initgenarate invalid type comment (#2773) (ede8a20), closes #2772 - config: handle
./in tsconfigpathsforpathsToModuleNameMapper(#2797) (42ff5e4), closes #2709
Code Refactoring
27.0.4 (2021-07-21)
Bug Fixes
- add
@types/jestas optionalpeerDependenciesto solve yarn 2 (#2756) (5fbf43e) - add
babel-jestas optionalpeerDependenciesto solve yarn 2 (#2751) (8bede2e) - config: include AST transformer's
nameandversioninto cache key (#2755) (310fb9a), closes #2753
Features
- link jest config types on
npx ts-jest:init(#2742) (f51ba05) - set env var
TS_JESTto allow detecting ofts-jest(#2717) (56c137a), closes #2716
27.0.3 (2021-06-06)
Bug Fixes
Features
27.0.2 (2021-05-30)
Bug Fixes
- compiler: add empty string file content to compiler cache (#2633) (0feb556), closes #2625
- config:
excludeshould only exclude files which match glob values (#2637) (c5ce979), closes #2634
27.0.1 (2021-05-26)
Bug Fixes
- cli: keep
testMatchif old jest config contains it (#2618) (c568f49), closes #2616 - compiler: make sure
isolatedModules: falseuse updated compiler options (#2628) (348e30f), closes #2629 - add missing export
presets(#2624) (0ea025e), closes #2623
v27.0.7
Bug Fixes
v27.0.6
Bug Fixes
v27.0.5
Bug Fixes
- cli: add migration
tsConfigoption forts-jestconfig options (#2794) (781710b), closes #2764 - cli: fix
config:initgenarate invalid type comment (#2773) (ede8a20), closes #2772 - config: handle
./in tsconfigpathsforpathsToModuleNameMapper(#2797) (42ff5e4), closes #2709
Code Refactoring
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @types/[email protected]
npm ERR! node_modules/@types/jest
npm ERR! dev @types/jest@"26.0.24" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @types/jest@"^27.0.0" from [email protected]
npm ERR! node_modules/ts-jest
npm ERR! dev ts-jest@"27.1.5" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @types/[email protected]
npm ERR! node_modules/@types/jest
npm ERR! peerOptional @types/jest@"^27.0.0" from [email protected]
npm ERR! node_modules/ts-jest
npm ERR! dev ts-jest@"27.1.5" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/worker/ab350b/14694d/cache/others/npm/_logs/2023-11-14T04_04_27_322Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /tmp/worker/ab350b/14694d/cache/others/npm/_logs/2023-11-14T04_04_27_322Z-debug-0.log