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
- ..
- invites
- access.rs
- account_deletion.rs
- admin.rs
- aliases.rs
- avatars.rs
- crypto.rs
- deletion.rs
- deploy_keys.rs
- device.rs
- directory.rs
- dock.rs
- email.rs
- emails.rs
- github.rs
- invites.rs
- job_tokens.rs
- lib.rs
- members.rs
- oauth.rs
- paid.rs
- people.rs
- profiles.rs
- rename.rs
- run_credentials.rs
- security.rs
- shared_invites.rs
- sounds.rs
- teams.rs
- throttle.rs
- token_reach.rs
- tokens.rs
- two_factor.rs
- workspaces.rs