fix(deps): update dependency pino-pretty to v11 #1835
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Important Auto Review SkippedBot user detected. To trigger a single review, invoke the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
![codecov[bot]](https://avatars.githubusercontent.com/in/254?s=60&v=4){kind=small}
There was a problem hiding this comment.
The changes appear to be routine package updates, which is a good practice. The pino-pretty package was updated from version 10.3.1 to 11.0.0. These updates help to make sure that the application uses the latest, most secure versions of the packages. The changes don't seem to cause any apparent issues.
| @@ -17,6 +17,6 @@ | |||
| "license": "ISC", | |||
| "dependencies": { | |||
| "pino": "^8.18.0", | |||
| "pino-pretty": "^10.3.1" | |||
| "pino-pretty": "^11.0.0" | |||
There was a problem hiding this comment.
This line updates the pino-pretty package in the package.json file. Please ensure that all features using this package have been thoroughly tested with the new version to ensure it doesn't introduce any breaking changes.
| @@ -131,8 +131,8 @@ importers: | |||
| specifier: ^8.18.0 | |||
| version: 8.19.0 | |||
| pino-pretty: | |||
| specifier: ^10.3.1 | |||
| version: 10.3.1 | |||
| specifier: ^11.0.0 | |||
There was a problem hiding this comment.
The pino-pretty package version has also been updated in the pnpm-lock.yaml file. This ensures consistency across the version mentioned in the package.json and the actual installed version.
| @@ -2092,8 +2092,8 @@ packages: | |||
| split2: 4.2.0 | |||
| dev: false | |||
|
|
|||
| /pino-pretty@10.3.1: | |||
| resolution: {integrity: sha512-az8JbIYeN/1iLj2t0jR9DV48/LQ3RC6hZPpapKPkb84Q+yTidMCpgWxIT3N0flnBDilyBQ1luWNpOeJptjdp/g==} | |||
| /pino-pretty@11.0.0: | |||
There was a problem hiding this comment.
This line updates the SHA512 integrity check for the new version of pino-pretty. It's excellent that this was updated, it ensures that the downloaded package hasn't been tampered with.
There was a problem hiding this comment.
The changes show an upgraded version of the pino-pretty package, both in the package.json file and in the lock file. While updating the package versions is good for getting improvements and security patches, it's important to test the application after making these changes to ensure that it doesn't break. In general, the changes look good.
| @@ -17,6 +17,6 @@ | |||
| "license": "ISC", | |||
| "dependencies": { | |||
| "pino": "^8.18.0", | |||
| "pino-pretty": "^10.3.1" | |||
| "pino-pretty": "^11.0.0" | |||
There was a problem hiding this comment.
The upgrade to pino-pretty v11.0.0 has breaking changes. Check all dependencies for compatibility, with particular attention to the logging format since that's what this module specializes in.
| @@ -131,8 +131,8 @@ importers: | |||
| specifier: ^8.18.0 | |||
| version: 8.19.0 | |||
| pino-pretty: | |||
| specifier: ^10.3.1 | |||
| version: 10.3.1 | |||
| specifier: ^11.0.0 | |||
There was a problem hiding this comment.
The version specifier for the pino-pretty package has been updated in the lock file as well. Please ensure the application's compatibility with this new version.
| @@ -2092,8 +2092,8 @@ packages: | |||
| split2: 4.2.0 | |||
| dev: false | |||
|
|
|||
| /pino-pretty@10.3.1: | |||
| resolution: {integrity: sha512-az8JbIYeN/1iLj2t0jR9DV48/LQ3RC6hZPpapKPkb84Q+yTidMCpgWxIT3N0flnBDilyBQ1luWNpOeJptjdp/g==} | |||
| /pino-pretty@11.0.0: | |||
There was a problem hiding this comment.
You've updated the integrity hash here. This is a generally good practice as it offers a form of data integrity guarantee. Although, it is recommended to verify this integrity hash with the source repository.
|
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ 🚮 Removed packages: npm/pino-pretty@10.3.1 |
|
Here's the code health analysis summary for commits Analysis Summary
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found Additional details and impacted files@@ Coverage Diff @@
## main #1835 +/- ##
=======================================
Coverage 41.76% 41.76%
=======================================
Files 83 83
Lines 10273 10273
Branches 169 168 -1
=======================================
Hits 4291 4291
Misses 5982 5982
☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/pino-pretty-11.x
branch
from
661c669
to
e42c533
Compare
| specifier: ^10.3.1 | ||
| version: 10.3.1 | ||
| specifier: ^11.0.0 | ||
| version: 11.0.0 |
There was a problem hiding this comment.
It's great that the version upgrade was also reflected in the pnpm-lock.yaml file, which ensures consistency across environments. It is still necessary to ensure that this change is tested adequately.
| specifier: ^10.3.1 | ||
| version: 10.3.1 | ||
| specifier: ^11.0.0 | ||
| version: 11.0.0 |
There was a problem hiding this comment.
The change in version is correctly reflected in pnpm-lock.yaml as well. This is good as it helps ensure the same version of the package is installed.
This PR contains the following updates:
^10.3.1->^11.0.0Release Notes
pinojs/pino-pretty (pino-pretty)
v11.0.0Compare Source
What's Changed
New Contributors
Full Changelog: pinojs/pino-pretty@v10.3.1...v11.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.