Skip to content

v1.4.2

Latest

Choose a tag to compare

@github-actions github-actions released this 17 Nov 01:09
· 51 commits to main since this release
Immutable release. Only release title and notes can be modified.
da82720

Added

  • The repository is licensed under the Apache License 2.0, as the other NCodeGroup repositories are: LICENSE.txt holds the license and COPYRIGHT.txt the copyright notice.
  • .git-blame-ignore-revs lists the commits of the one-time Biome reformat, so GitHub's blame view and git blame (with git config blame.ignoreRevsFile .git-blame-ignore-revs) show who last changed a line instead of the reformat (#212, ADR-1010).

Changed

  • GOVERNANCE.md, ROADMAP.md, docs/architecture.md and docs/assurance-case.md describe code-review itself: its maintainer, its plans for the next twelve months, its components and design rules, and its security requirements, threat model and the weaknesses it counters (#206).
  • README.md shows the OpenSSF Best Practices badge (project 16752, passing) and says how to verify a release with gh release verify, and docs/best-practices-badge.md records where the silver level stands.
  • CI runs npm run lint, which fails on TypeScript that Biome's formatter or linter doesn't accept as biome.json sets them, and npm run format applies them; the code is reformatted once to match, and AGENTS.md, CONTRIBUTING.md and docs/best-practices-badge.md say so (#210, ADR-1010).
  • The repository follows project-template v0.99.0 (from v0.96.0): it gains the /best-practices command, which checks the OpenSSF Best Practices answers against the repository, and docs/best-practices-criteria.md, which maps every criterion to its evidence; tag-release.yml runs CI on a release's commit before it tags it and signs the tag with gitsign, which SECURITY.md and README.md say how to check; CONTRIBUTING.md has a Review Requirements section, SECURITY.md promises an acknowledgement within 14 days, and docs/assurance-case.md has a Security Reviews section.

Fixed

  • The action loads again: action.yml, from 1.4.0 on, wrote the approve input's description as a plain YAML scalar holding : , which GitHub's runner can't parse, so every job that used the action failed in "Set up job". A test parses action.yml as YAML (#221).