Giters

beaussan / nest-onion-boilerplate

A starter kit for production ready Nestjs application

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

An in-range update of @nestjs/jwt is breaking the build 🚨

greenkeeper opened this issue · comments

commented

The dependency @nestjs/jwt was updated from 6.1.1 to 6.1.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@nestjs/jwt is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ✅ ci/circleci: build: Your tests passed on CircleCI! (Details).
  • ❌ ci/circleci: back-test-e2e: CircleCI is running your tests (Details).
  • ❌ ci/circleci: lint: CircleCI is running your tests (Details).
  • ❌ ci/circleci: back-test-unit: Your tests failed on CircleCI (Details).
Commits

The new version differs by 178 commits.

  • 44a5a6f chore(): release v6.1.2
  • 2ca80d0 feat(): migrate to eslint, add commitlint
  • e7d096d Merge branch 'EJMason-bugfix/allow-buffer-keys'
  • 7660f66 fix(): revert typings to avoid breaking change
  • c722dbd Merge branch 'bugfix/allow-buffer-keys' of https://github.com/EJMason/jwt into EJMason-bugfix/allow-buffer-keys
  • d5f4cb9 chore(deps): update dependency typescript to v3.8.2
  • 6ee5e14 chore(deps): update nest monorepo to v6.11.8
  • e274327 chore(deps): update dependency @types/jest to v25.1.3
  • e24b7bd chore(deps): update dependency ts-jest to v25.2.1
  • 04511b1 Update README.md
  • 8db39f3 chore(deps): update nest monorepo to v6.11.7
  • 0326da3 chore(deps): update dependency husky to v4.2.3
  • 8af1d13 chore(deps): update dependency husky to v4.2.2
  • 60f6f5f chore(deps): update dependency @types/jest to v25.1.2
  • a20105e chore(deps): update nest monorepo to v6.11.6

There are 178 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

commented

After pinning to 6.1.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.