Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.162.0→2.163.02.162.0→2.163.02.162.0→2.163.0Release Notes
node-opcua/node-opcua (node-opcua)
v2.163.0: 🚀 Release Notes — v2.163.0Compare Source
This release is a major step forward for DataType handling performance and OPC UA 1.05 compliance. It introduces a new lazy and parallel DataType extraction pipeline, significantly improving scalability for large and complex information models. In parallel, full support for OPC UA 1.05 subtyped structures and unions has been finalized, alongside multiple performance optimizations, correctness fixes, and test expansions.
✨ TL;DR
🌟 Key Features & Enhancements
🧠 Lazy & Parallel DataType Extraction
3ad017cIntroduced a Lazy DataTypeExtractStrategy to efficiently handle very large DataType trees:984510cMajor performance refactor:57374f8Prefetch dependent field DataTypes in parallel during schema extraction:🧬 OPC UA 1.05 — Subtyped Structures & Unions
4e02e64Added full support for OPC UA 1.05 subtyped fields:17ea9bbFixed client-side creation of ExtensionObjects containing subtyped fields (client)📌 Summary
Version 2.163.0 delivers substantial scalability gains for complex OPC UA servers and clients, especially those with large DataType graphs or OPC UA 1.05 models. Lazy, parallel extraction dramatically reduces startup time and network load while maintaining strict correctness and backward compatibility.
💙 Support the project
Consider joining the NodeOPCUA Subscription program
for professional support, or help sustain the project by sponsoring us on OpenCollective
.
Full Changelog: node-opcua/node-opcua@v2.162.0...v2.163.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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.