Skip to content

Conversation

@aryamohanan
Copy link
Contributor

@aryamohanan aryamohanan commented Sep 18, 2025

This PR pins pino to version 9.9.5 to avoid compatibility issues in v9.10.0.

Issue:

The pipeline v18.18 ESM is failing due to the latest Pino update.

It throws

TypeError: diagChan.tracingChannel is not a function

because tracingChannel() is not available in Node.js v18.18.

This method was added in the latest Pino release, pino#2281 and diagnostics_channel.tracingChannel was introduced in Node.js starting from v18.19 (see Node.js docs).

An issue has been created in the Pino repo regarding this incompatibility.

@aryamohanan aryamohanan changed the title fix: pin pino version to support v18.18 fix: pinned pino to v9.9.5 to avoid compatibility issues on v18.18 Sep 18, 2025
@aryamohanan aryamohanan marked this pull request as ready for review September 18, 2025 06:43
@aryamohanan aryamohanan requested a review from a team as a code owner September 18, 2025 06:43
Copy link
Contributor

@abhilash-sivan abhilash-sivan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can reenable updates once we remove node v18 from support or the issue gets resolved

Copy link
Contributor

@kirrg001 kirrg001 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

We need a blocker JIRA issue to revert this change 👍

fix: resolved pino compatibility issues for v18

@aryamohanan
Copy link
Contributor Author

created card to revert the change https://jsw.ibm.com/browse/INSTA-55339

@aryamohanan aryamohanan changed the title fix: pinned pino to v9.9.5 to avoid compatibility issues on v18.18 fix: resolved pino compatibility issues for v18 Sep 18, 2025
@aryamohanan aryamohanan merged commit a286f29 into main Sep 18, 2025
2 checks passed
@MukulWBD
Copy link

I am still facing the same issue even after you reverted the latest updates.
{08F9704B-3C4F-4B39-A63F-07ECAE3F54A4}

@aryamohanan
Copy link
Contributor Author

@MukulWBD The actual issue has been reported here: pinojs/pino#2289. Please share your concern on that thread.
We have pinned an unaffected version in our package, but the root issue remains and will need to be resolved by the Pino team. Kindly follow the issue for updates.

aryamohanan added a commit that referenced this pull request Sep 22, 2025
aryamohanan added a commit that referenced this pull request Sep 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants