# @pnpm/deps.inspection.peers-issues-renderer

## 1100.0.7

### Patch Changes

- Updated dependencies:
  - @pnpm/types@1101.4.0

## 1100.0.6

### Patch Changes

- Updated dependencies [681b593]
  - @pnpm/types@1101.3.2

## 1100.0.5

### Patch Changes

- Updated dependencies [bf1b731]
  - @pnpm/types@1101.3.1

## 1100.0.4

### Patch Changes

- Updated dependencies [a017bf3]
  - @pnpm/types@1101.3.0

## 1100.0.3

### Patch Changes

- Updated dependencies [35d2355]
  - @pnpm/types@1101.2.0

## 1100.0.2

### Patch Changes

- Updated dependencies [64afc92]
  - @pnpm/types@1101.1.1

## 1100.0.1

### Patch Changes

- Updated dependencies [b61e268]
  - @pnpm/types@1101.1.0

## 1100.0.0

### Minor Changes

- 0b2f86e: When `strictPeerDependencies` is `true`, the `ERR_PNPM_PEER_DEP_ISSUES` error once again renders the peer dependency issues inline using the same format as `pnpm peers check`, so users (and CI tools like Renovate) can see what failed without running `pnpm peers check` separately [#11439](https://github.com/pnpm/pnpm/issues/11439).
