syntaqxA runner release publishes its sandbox images again. Each build job caches its target folder between releases, and that brought back the last release's target/runner-release/0.3.0 beside the new version's, so both went up in the job's files: the container image job's `cp release/*/g1t-runner-linux-x64` found two programs and stopped, the sandbox images were skipped after it, and 0.3.1 went out signed but without its sandbox section, so a computer setting up the sandbox for the first time waits for images. The build jobs now start from an empty target/runner-release, and the image and sandbox jobs name the version's own folder rather than a wildcard.6cd2cc0History
- ..
- anchors.yml
- artifacts.yml
- branches-ignore.yml
- cache.yml
- codeql.yml
- concurrency.yml
- container-job.yml
- defaults.yml
- dependabot-automerge.yml
- description-and-env.yml
- docker-action.yml
- docker-publish.yml
- environments.yml
- g1t-extension.yml
- go.yml
- if-expressions.yml
- issue-comment.yml
- java-gradle.yml
- job-options.yml
- labeler.yml
- many-events.yml
- matrix-from-json.yml
- max-parallel-expression.yml
- merge-queue.yml
- multiline-and-quotes.yml
- needs-outputs.yml
- node-matrix.yml
- on-null-events.yml
- pages.yml
- permissions-all.yml
- pr-review.yml
- pr-target-paths.yml
- publish-npm.yml
- python-package.yml
- release-on-tag.yml
- repository-dispatch.yml
- reusable-called.yml
- reusable-caller.yml
- runs-on-forms.yml
- rust-ci.yml
- sccache-like.yml
- schedule.yml
- services-postgres.yml
- single-event-string.yml
- stale.yml
- step-options.yml
- workflow-call-and-dispatch.yml
- workflow-dispatch-inputs.yml
- workflow-run.yml