dohertj2/mxaccessgw
1
0
Fork 0
Code Issues 43 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Publish Contracts + Client 0.3.0 (AcknowledgeAlarmRequest operator_password/operator_domain from 488649c) #214

New Issue
Closed
opened 2026-11-06 15:42:10 -05:00 by dohertj2 · 1 comment
dohertj2 commented 2026-11-06 15:42:10 -05:00
Owner
Copy Link
Copy Source

Main 488649c (2026-10-20) added operator_password / operator_domain to AcknowledgeAlarmRequest, but MxGateway.Contracts and MxGateway.Client csproj still declare 0.2.1 and the feed's newest is 0.2.1 (2026-08-25, no OperatorPassword). Bump both to 0.3.0 (additive proto change) and publish so OtOpcUa can adopt.

Blocks lmxopcua#749; related #170.

Main `488649c` (2026-10-20) added `operator_password` / `operator_domain` to `AcknowledgeAlarmRequest`, but `MxGateway.Contracts` and `MxGateway.Client` csproj still declare `0.2.1` and the feed's newest is `0.2.1` (2026-08-25, no `OperatorPassword`). Bump both to `0.3.0` (additive proto change) and publish so OtOpcUa can adopt. Blocks lmxopcua#749; related #170.
dohertj2 added the priority:p1type:followupcross-repo labels 2026-11-06 15:42:10 -05:00
dohertj2 commented 2026-11-06 16:00:45 -05:00
Author
Owner
Copy Link
Copy Source

Published. The version bump is on main in e5e7f18.

  • ZB.MOM.WW.MxGateway.Contracts and ZB.MOM.WW.MxGateway.Client go from 0.2.1 to 0.3.0 (<Version> in src/ZB.MOM.WW.MxGateway.Contracts/ZB.MOM.WW.MxGateway.Contracts.csproj and clients/dotnet/ZB.MOM.WW.MxGateway.Client/ZB.MOM.WW.MxGateway.Client.csproj). The clients/dotnet/README.md install line and docs/ClientPackaging.md are updated to match.
  • Lockstep check: these two are the only packable .NET projects (IsPackable=true). They release together through Invoke-PackDotnet. src/Directory.Build.props's 0.1.2 stamps the Server/Worker/test assemblies, isn't part of the published set, and is unchanged. The Python, Rust, Java and Go clients have their own manifests and weren't republished.
  • Verification before publishing:
    • .NET client tests: 148 passed / 1 skipped.
    • Packed Contracts 0.3.0: reflection over lib/net10.0 confirms AcknowledgeAlarmRequest.OperatorPassword (field 6) and OperatorDomain (field 7). Both net10.0 and net48 dlls contain get_/set_OperatorPassword; the old 0.2.1 dll has 0 occurrences.
    • The Client nuspec depends on Contracts 0.3.0.
  • Published the same way scripts/pack-clients.ps1 -Publish does: a Gitea API pre-check (404 for both), then dotnet nuget push ... --source https://gitea.dohertylan.com/api/packages/dohertj2/nuget/index.json --api-key $GITEA_TOKEN, Contracts first. The snupkgs were pushed too.
  • The feed registration now lists 0.1.0, 0.1.1, 0.1.2, 0.2.0, 0.2.1, 0.3.0 for both zb.mom.ww.mxgateway.contracts and zb.mom.ww.mxgateway.client. The downloaded Contracts 0.3.0 nupkg is SHA-256 identical to the local pack (2a81ea8c…c045).

This unblocks lmxopcua#749.

Published. The version bump is on `main` in e5e7f18. - `ZB.MOM.WW.MxGateway.Contracts` and `ZB.MOM.WW.MxGateway.Client` go from 0.2.1 to **0.3.0** (`<Version>` in `src/ZB.MOM.WW.MxGateway.Contracts/ZB.MOM.WW.MxGateway.Contracts.csproj` and `clients/dotnet/ZB.MOM.WW.MxGateway.Client/ZB.MOM.WW.MxGateway.Client.csproj`). The `clients/dotnet/README.md` install line and `docs/ClientPackaging.md` are updated to match. - **Lockstep check:** these two are the only packable .NET projects (`IsPackable=true`). They release together through `Invoke-PackDotnet`. `src/Directory.Build.props`'s `0.1.2` stamps the Server/Worker/test assemblies, isn't part of the published set, and is unchanged. The Python, Rust, Java and Go clients have their own manifests and weren't republished. - Verification before publishing: - .NET client tests: 148 passed / 1 skipped. - Packed Contracts 0.3.0: reflection over `lib/net10.0` confirms `AcknowledgeAlarmRequest.OperatorPassword` (field 6) and `OperatorDomain` (field 7). Both net10.0 and net48 dlls contain `get_/set_OperatorPassword`; the old 0.2.1 dll has 0 occurrences. - The Client nuspec depends on Contracts 0.3.0. - Published the same way `scripts/pack-clients.ps1 -Publish` does: a Gitea API pre-check (404 for both), then `dotnet nuget push ... --source https://gitea.dohertylan.com/api/packages/dohertj2/nuget/index.json --api-key $GITEA_TOKEN`, Contracts first. The snupkgs were pushed too. - The feed registration now lists `0.1.0, 0.1.1, 0.1.2, 0.2.0, 0.2.1, 0.3.0` for both `zb.mom.ww.mxgateway.contracts` and `zb.mom.ww.mxgateway.client`. The downloaded Contracts 0.3.0 nupkg is SHA-256 identical to the local pack (`2a81ea8c…c045`). This unblocks lmxopcua#749.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area:auth
Authentication and authorization
 area:client-dotnet
.NET client library
 area:client-go
Go client library
 area:client-java
Java client library
 area:client-python
Python client library
 area:client-rust
Rust client library
 area:contracts
Protocol and generated contract work
 area:dashboard
Blazor dashboard work
 area:docs
Documentation
 area:gateway
Gateway server work
 area:tests
Automated and live tests
 area:worker
MXAccess worker process work
 blocked
Blocked by dependency
 cross-repo
Needs coordinated change in another family repo (wire contract etc.)
 migrated
Migrated from a markdown backlog (2026-11 standardization)
 priority:p0
Must-have / blocking
 priority:p1
High priority
 priority:p2
Normal priority
 priority:p3
Low priority / nice to have
 type:bug
Defect in shipped behaviour
 type:debt
Technical debt / hygiene
 type:deploy-gate
Rollout/deploy/migration step not yet done on an environment
 type:docs
Documentation work
 type:feature
Feature implementation
 type:followup
Follow-up deferred from a plan, PR or gate
 type:infra
Infrastructure and scaffolding
 type:review-finding
Unfixed finding from an architecture/code review
 type:test
Test work
No Label cross-repo priority:p1 type:followup
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/mxaccessgw#214
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?