Vion.Contracts 0.2.0

Vion.Contracts

Shared contracts — MQTT topics, payloads, FlatBuffers schemas, and introspection models — used by the Vion Dale SDK and the Vion Dale runtime.

This package exists as its own repository because it is consumed by both public and private code, and has a release cadence independent of either.

Install

dotnet add package Vion.Contracts

Targets netstandard2.1.

Source-available

This repository is source-available. Issues and pull requests are not accepted from outside the vion-iot organization. For questions or to report a problem, see SUPPORT.md.

Releases

Versions are driven by git tags. There is no version number in any .csproj.

Cutting a release

Prerequisites:

• main is green on the commit you want to release.
• You have gh installed and authenticated (gh auth status).

# Stable release:
gh release create v0.2.0 --target main --generate-notes \
  --title "v0.2.0" --notes "Short release summary."

# Pre-release (add --prerelease for the UI badge; NuGet detects pre-release
# automatically from the SemVer suffix):
gh release create v0.2.0-preview.1 --target main --prerelease --generate-notes \
  --title "v0.2.0-preview.1" --notes "What this preview validates."

Creating the release pushes the tag, which triggers publish.yml:

1. Builds and packs with Version taken from the tag (strips the v prefix).
2. Pushes .nupkg + .snupkg to the private Azure DevOps feed.
3. Publishes to nuget.org using Trusted Publishing (short-lived OIDC token — no API key stored).

Verify the result under the VION-IoT profile on nuget.org.

Version immutability

Once a version is published to nuget.org, the version ID is permanent. You can unlist a version (which hides it from search and dotnet add package), but the ID stays burned — you cannot re-upload the same version, even after yanking. Pick the next number for any subsequent change, even a tiny fix.

Required configuration

One-time setup per repo; flag this if you fork or rotate credentials:

• GitHub secret AZURE_DEVOPS_PAT — PAT with Packaging: Read & write on the Azure DevOps feed.
• GitHub secret NUGET_USER — individual nuget.org username that is a member of the org owning the Trusted Publishing policy. Not the org name. (Docs use contoso-bot as the example — this matters; setting it to the org name produces No matching trust policy owned by user 'X' was found.)
• Trusted Publishing policy on nuget.org: Package Owner VION-IoT (the org), Repository Owner VION-IoT, Repository vion-contracts, Workflow File publish.yml. See NuGet's Trusted Publishing docs for the UI walkthrough.

License

Apache 2.0 — see LICENSE.