Skip to content

Release 1.2.0

Choose a tag to compare

View all tags
@cdcavell cdcavell released this 21 Jun 04:02
· 35 commits to main since this release
v1.2.0
136a601
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Summary

1.2.0 is a compatible minor release for the stable 1.x AsiBackbone package family.

This release prepares the project for the current 1.2.x stable line by aligning release metadata, NuGet package metadata, documentation, template behavior, release validation guidance, and public project wording around the current package family.

No breaking public API changes are intended.

In this software project, ASI means Accountable Systems Infrastructure. AsiBackbone remains a governance-spine package family for accountable .NET decision flow; it is not an artificial superintelligence implementation, AI model host, robot controller, compliance guarantee, immutable ledger, or production tamper-evidence provider by itself.

Highlights

  • Promoted release metadata from 1.1.1 to 1.2.0.
  • Preserved AssemblyVersion as 1.0.0.0 for the compatible stable 1.x line.
  • Updated package Version, FileVersion, and InformationalVersion for 1.2.0.
  • Added dedicated 1.2.0 release notes.
  • Added a 1.2.0 release readiness record.
  • Updated README, documentation home, article index, DocFX navigation, API compatibility guidance, release validation guidance, quality documentation, citation metadata, and Zenodo metadata for the 1.2.x package family.
  • Updated template package references for 1.2.0.
  • Fixed release-validation issues around template content packing, template content compilation, DocFX metadata inspection, and NuGet README metadata validation.

Stable package family

The 1.2.0 release covers the following package family:

  • CDCavell.AsiBackbone.Core
  • CDCavell.AsiBackbone.DependencyInjection
  • CDCavell.AsiBackbone.Storage.InMemory
  • CDCavell.AsiBackbone.EntityFrameworkCore
  • CDCavell.AsiBackbone.AspNetCore
  • CDCavell.AsiBackbone.Testing
  • CDCavell.AsiBackbone.Templates
  • CDCavell.AsiBackbone.Analyzers
  • CDCavell.AsiBackbone.OpenTelemetry
  • CDCavell.AsiBackbone.Signing.LocalDevelopment
  • CDCavell.AsiBackbone.Signing.ManagedKey

Compatibility notes

1.2.0 is a compatible minor release in the stable 1.x line.

Existing stable 1.x consumers should be able to upgrade without required source-code changes for existing APIs.

The release continues the project’s stable binary identity strategy:

  • Package Version: 1.2.0
  • AssemblyVersion: 1.0.0.0
  • FileVersion: 1.2.0.0
  • InformationalVersion: 1.2.0+...

Documentation updates

This release aligns the documentation set around the current stable 1.2.x package family, including:

  • implementation-first adoption guidance;
  • package-family boundaries;
  • release validation process;
  • API compatibility and SemVer guidance;
  • template usage;
  • quality posture;
  • release readiness tracking;
  • public wording and non-claim boundaries.

Template and validation fixes

This release also includes release-preparation fixes discovered during validation:

  • Excluded inner template content projects from smoke-test package packing.
  • Prevented template .cs scaffold files from compiling as part of the template package project.
  • Allowed the inner template project to resolve local AsiBackbone project references when inspected inside the repository.
  • Updated NuGet metadata validation so README package-family checks are derived from the expected release version instead of being hard-coded to 1.1.x.

Boundary notes

AsiBackbone remains Accountable Systems Infrastructure for governed .NET decision flow.

The host application remains responsible for:

  • authentication and authorization;
  • persistence provider selection;
  • database migrations;
  • execution behavior;
  • DLP/classification implementation;
  • signing provider selection;
  • key custody;
  • verification policy;
  • storage immutability;
  • telemetry exporter configuration;
  • legal, compliance, and operational accountability.

Event Hubs, Purview, Azure-specific SDK adapters, robotics, immutable-storage, external anchoring, and additional provider packages remain outside the 1.2.0 stable package contract unless separately reviewed and released.

Validation

Release validation should include:

  • CI
  • Stable Release Validation
  • Version Consistency
  • DocFX documentation build
  • Package creation
  • Generated NuGet metadata validation
  • Template package smoke validation
  • External consumer smoke test
  • Stable package integration smoke test

Related

  • Issue: #315
  • Release preparation PR: #336
Assets 2
Loading