v1.3.0

Summary

Four new optional keys under ci change the G3 workflow. Without them, each rendered file is the same as in 1.2.1.

• ci.env and ci.secrets add an env: block to the All checks step (#163).
• ci.setup adds steps before Install, for example a Node setup with a package cache (#162).
• ci.branches limits K6, K7, K14, and K20 to PRs into the listed base branches (#164). A promotion PR, for example dev to staging, then runs only the other checks.

Config changes

Key	Default	Note
ci.env	none	A map of NAME: value for the All checks step. Plain values only (D72).
ci.secrets	none	A list of repo secret names. The step gets ${{ secrets.NAME }} (D72).
ci.setup	none	node adds a pinned actions/setup-node step with cache: npm. steps adds uses, with, and run items (D73).
ci.branches	none	A list of base branches. It must list branches.integration (D74).

Changed generated files

• .github/workflows/cornerstone-checks.yml: it changes only if you set one of the new keys.

Steps

1. Set framework_version to 1.3.0, and run stone render.
2. To pass a secret to the tests, add it as a repo secret. List its name in ci.secrets.
3. If a test reads a secret, make it skip when the value is empty. A PR from a fork gets an empty value.
4. To skip the ticket checks on promotion PRs, set ci.branches to the base branches of the ticket PRs. For example, use [dev].
5. If you set ci.branches, require a human review on each base branch that is not in the list (G5).
6. After a change to the config, run stone render.
7. Commit the changed generated files alone, with the trailers Role: generator and Actor: agent.

Also in this release

One place now checks the keys under ci, so a wrong key gives one error (#181).