Skip to content

chore(binding-opcua): upgrade node-opcua family to 2.179.0 - #1553

Open
erossignon wants to merge 1 commit into
eclipse-thingweb:masterfrom
node-opcua:core/update_node-opcua
Open

chore(binding-opcua): upgrade node-opcua family to 2.179.0#1553
erossignon wants to merge 1 commit into
eclipse-thingweb:masterfrom
node-opcua:core/update_node-opcua

Conversation

@erossignon

Copy link
Copy Markdown
Contributor

Bumps all node-opcua-* packages to 2.179.0 (node-opcua-crypto to 5.9.0).

These packages release together and must be upgraded as a set, so per-package dependabot PRs can't build. Replaces #1549 and #1551 — both can be closed.

Needed by crypto 5: x509 identity uses clientCertificateManager.getPrivateKey(), and skipLibCheck in the examples tsconfig for the transitive asn1-schema ESM typings.

npm run ncu:opcua is the upgrade procedure, now documented in the binding README.

All 73 binding-opcua tests pass.

The node-opcua-* packages must be bumped as one set, which dependabot
cannot do. Use `npm run ncu:opcua` at the root instead.

node-opcua-crypto 5 drops the sync readPrivateKey, so the x509 identity
now uses clientCertificateManager.getPrivateKey(). Its ESM-only
asn1-schema typings need skipLibCheck in the examples tsconfig.
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.

1 participant