SSL Certificate Expired on npm.bryntum.com

[Qwerty]

Hello Bryntum Support,

We are currently unable to install @bryntum/gantt-lib from your private npm registry due to an expired SSL certificate on https://npm.bryntum.com.

When running yarn install, we encounter the following error:

[2/4] Fetching packages...
error Error: certificate has expired
at TLSSocket.onConnectSecure (node:tls_wrap34)
at TLSSocket.emit (node:events:513:28)
at TLSSocket.finishInit (node:tls_wrap:953:8)
at TLSWrap.ssl.onhandshakedone (node:tls_wrap:734:12)
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error https://npm.bryntum.com/@bryntum%2fgantt-lib/-/gantt-lib-1.0.0.tgz: certificate has expired

This issue is blocking our builds and deployments since we cannot fetch the package over a secure connection.

Steps to reproduce:

Run yarn install in a project using @bryntum/gantt-lib with registry https://npm.bryntum.com.

Observe SSL certificate error.

Impact:

Builds are failing in CI/CD pipelines.

Local developer environments are unable to install dependencies.

Request:
Could you please renew or update the SSL certificate for npm.bryntum.com at the earliest?
In the meantime, please let us know if you recommend any temporary workaround from your side.

Thank you for your support.

Best regards,
Amplify-Now

[shubham jain]

+1 Experiencing the same issue. We're currently unable to download the Bryntum packages due to a CERT_HAS_EXPIRED error, which has disrupted our build pipelines. Kindly prioritize resolving this issue as it’s impacting our development workflows.

npm ERR! code CERT_HAS_EXPIRED
npm ERR! errno CERT_HAS_EXPIRED
npm ERR! request to https://npm.bryntum.com/@bryntum%2fscheduler-lib/-/scheduler-lib-1.0.0.tgz failed, reason: certificate has expired

[tasnim]

Hello shubham,

Thank you for reaching out and for providing a clear, detailed report. We sincerely apologize for the inconvenience this is causing.

We are aware of the expired SSL certificate on npm.bryntum.com and are working to resolve the issue as quickly as possible. We understand that this is blocking your builds and deployments, and we are treating this with the highest priority.

We will notify you as soon as the certificate has been renewed and the registry is back to normal.

[tasnim]

The issue has been resolved. Could you please try again and confirm if it works on your side!

[Qwerty]

It worked for us. Thanks

[shubham jain]

It works now. Thanks for the quick turnaround Tasnim.