Skip to content

v0.106.0

Choose a tag to compare

@github-actions github-actions released this 20 Nov 04:46
· 228 commits to main since this release
39e23a6

Added

  • Once version.json exists, .template/Update-Project.ps1 and Adopt-Project.ps1 name each job of the project's own workflows, other than publish.yml, that builds, packs, tests or pushes packages with an actions/checkout step without fetch-depth: 0, on which Nerdbank.GitVersioning fails the build, or with a -p:Version argument, which it ignores. (#443, ADR-0138)
  • With NCode Review, .template/Update-Project.ps1 says what code-review.yml and AGENTS.md still lack for its approval, also when the project is already up to date: a pin before v1.4.0, no approve: true or no draft: yes, and to run tools/Set-RepositoryBaseline.ps1 again afterwards. (#438, ADR-0022)

Changed

  • A .NET library whose own workflow pushes its NuGet packages, which already got no publish.yml, gets no release-provenance.yml or raise-baseline.yml either, since only publish.yml calls them, and an update deletes the ones an earlier update added. SECURITY.md, GOVERNANCE.md, docs/architecture.md, docs/assurance-case.md, docs/best-practices-badge.md, docs/api-compatibility.md and docs/best-practices-criteria.md name that workflow instead of describing publish.yml, trusted publishing, the nuget environment and provenance. The new nuget_publisher answer, which the update and the adoption work out from the workflows that run nuget push, records it. (#444, ADR-0151)
  • SECURITY.md says how to verify a release tag's gitsign signature only when AGENTS.md's Landing section tags releases (release: tag or tag+release), and the update shows its change that way: the new release_policy answer, never recorded, which the update and the adoption read from that line, writes the line in a new project's AGENTS.md. docs/best-practices-criteria.md's version_tags_signed row names the same condition. (#444, ADR-0028)