Skip to content

Bump node-opcua from 2.175.3 to 2.176.0 - #59

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/node-opcua-2.176.0
Closed

Bump node-opcua from 2.175.3 to 2.176.0#59
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/node-opcua-2.176.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 13, 2026

Copy link
Copy Markdown

Bumps node-opcua from 2.175.3 to 2.176.0.

Release notes

Sourced from node-opcua's releases.

v2.176.0

node-opcua 2.176.0 — release notes

This release covers all changes between v2.175.6 and v2.176.0, and it is a big one: two long-requested OPC UA capabilities land at the same time, both implemented on the client and the server side.

  • AliasNames (OPC 10000-17) — name your Nodes the way your plant already names them.
  • Reverse Connect (Part 6 §7.1.3) — let a Server behind a firewall dial out to the Client.

Alongside them, this release restores NodeSet2 access-control fidelity, removes a quadratic cost in address-space construction, and hardens two randomness defects found on the way.


✨ AliasNames — OPC 10000-17, server and client

node-opcua/node-opcua#1553

AliasNames are, in effect, DNS for an address space. A Client asks for the plant tag TI101 and gets back the NodeId it currently resolves to, instead of being configured with that raw NodeId in advance — a NodeId that changes every time the model is regenerated. It is the standard bridge between ISA-5.1 style tag names and explicitly modelled OPC UA Nodes.

Why this probably already concerns you

Every node-opcua Server that loads the standard nodeset already publishes Aliases, TagVariables and Topics, each carrying a MANDATORY FindAlias Method. Until now that Method was bound to nothing: a conformance tester saw the Server advertise the AliasName feature and then fail its only required Method. AliasNameVerboseDataType had no generated class at all. Both gaps are now closed.

One call to enable it

import { installAliasNames } from "node-opcua-alias-name-server";
await server.initialize();
await installAliasNames(server);   // also declares the ALIAS capability for discovery
await server.start();

That binds FindAlias, FindAliasVerbose and — when explicitly enabled — the configuration Methods, on Aliases, TagVariables, Topics and every vendor subcategory beneath them. If your NodeSet2.xml already models AliasNameType instances, nothing else is needed: the default store reads the address space directly. A Server that keeps its aliases elsewhere injects its own IAliasStore.

Three ways to declare an alias

... (truncated)

Commits
  • a456983 v2.176.0
  • 7e1a8b6 test(utils): skip the countUpperCase benchmark when instrumented
  • ea19189 test(reverse-connect): enable leak detection on unit tests, name ports consis...
  • fdf1d0a feat(address-space): split the NodeSet2 policy switch, AccessRestrictions opt-in
  • 319c89f fix(pseudo-session): do not assert on a Server's answer for method arguments
  • 7429a40 fix(address-space): gate AccessLevel export on the node class, per #1552 AC5
  • be62f94 fix(address-space): close issue #1552 and document the NodeSet2 policy work
  • d3dde97 fix(address-space): treat Anonymous as the baseline Role of every Session
  • a2b49a6 chore(random): check max value test
  • 96c43ad feat(address-space): separate trusted in-process callers from unresolved iden...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [node-opcua](https://github.com/node-opcua/node-opcua) from 2.175.3 to 2.176.0.
- [Release notes](https://github.com/node-opcua/node-opcua/releases)
- [Changelog](https://github.com/node-opcua/node-opcua/blob/master/RELEASE_NOTES.md)
- [Commits](node-opcua/node-opcua@v2.175.3...v2.176.0)

---
updated-dependencies:
- dependency-name: node-opcua
  dependency-version: 2.176.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 13, 2026
@dependabot @github

dependabot Bot commented on behalf of github Aug 20, 2026

Copy link
Copy Markdown
Author

Superseded by #60.

@dependabot dependabot Bot closed this Aug 20, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/node-opcua-2.176.0 branch August 20, 2026 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants