Skip to content

Release notes

1.1.0

A backup node now refuses writes its master would discard.

On a redundant pair, a project_resource_write sent to the backup used to answer "status":"written", and the change was then deleted by the master's next sync, including on a backup that had taken over during a failover. Mutating calls are now classified as Persistent, Runtime or Node-local:

  • a backup refuses every Persistent write, at any activity level;
  • a node that is not Active refuses Runtime writes (tag values, alarm acknowledge and shelving, Perspective sessions, script endpoints);
  • Node-local writes are unaffected.

Dry runs are refused the same way. policy_explain gains a redundancy row ahead of the mutation allowlists, and mcp_status and /data/artek-mcp/status gain a node block naming this node's role and activity level. Standalone gateways are unaffected. See Redundant pairs.

1.0.0

First release under the Artek, LLC certificate. Version numbering starts at 1.0.0.

  • Signed with the Artek, LLC certificate (SHA-1 99e472815b3417abab93e1c744c76699c73375d2). Ignition lists the vendor as "Artek, LLC".
  • On a gateway running a build from before the numbering restart, the Modules page shows the version going down. That is expected: this release is the newer one.
  • The module id (com.artek.mcp) is unchanged, so it installs as an upgrade and keeps your configuration. The gateway asks once to accept the new certificate.
  • Functionally identical to the last build before the restart. No change to the license agreement.
  • Headless upgrades: set the modules.json entry's certFingerprint to the fingerprint above in the same edit as filename, and make sure the entry carries licenseAgreementHash (3248084803). See Install.