Skip to content

RELEASE.md

Latest commit

 

History

History
44 lines (32 loc) · 2.11 KB

RELEASE.md

File metadata and controls

44 lines (32 loc) · 2.11 KB
Raw

Release Model

This repository follows the Lightning IT shared release and quality model.

Repository Classification

  • Repository: documentation
  • Type: generic_managed
  • Release type: none
  • Artifact type: none
  • Visibility: public
  • Release evidence: disabled
  • Heavy Incus release validation: not required

Branch Flow

  • develop is the integration branch for normal work, Renovate updates, and centrally managed synchronization.
  • main is the protected release branch.
  • This repository does not publish release artifacts; main still represents the protected stable branch.
  • A develop to main promotion PR is created automatically when releasable changes exist.
  • The develop to main PR is a manual gate and must never be auto-merged.
  • After main changes, a main to develop backmerge PR is created or updated automatically.
  • Integration and backmerge PRs may auto-merge only after required checks pass, all review conversations are resolved, and there are no conflicts.

Mandatory Quality Gates

  • Required profiles: repository-structure.
  • OS matrix: ubuntu-latest.
  • Product/runtime matrix: generic.
  • Fork pull requests run validation without publishing credentials.
  • Publishing secrets are available only to trusted main release workflows.
  • GitHub token permissions must stay least-privilege for each workflow.

Managed Repository Release

  • CI validates repository structure and file formats appropriate to the repository contents.
  • Generated documentation is maintained by shared-assets-lit.
  • Artifact/version behavior is documented in repository-specific files when artifacts are published.

Release Evidence

Release evidence is disabled because this repository does not publish release artifacts. Evidence records the repository name, repository type, version, tag, commit SHA, workflow run, tested matrix combinations, passed/failed/skipped jobs, built artifacts, published artifacts, changelog link, security scan result, and SBOM/provenance/signature links when available.

Evidence files must not contain tokens, credentials, private inventory values, or secret material.