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
- ..
- accounts.rs
- ai.rs
- attribution.rs
- budget.rs
- cards.rs
- catalogue.rs
- catalogue_tests.rs
- charged.rs
- closing.rs
- compute.rs
- costs.rs
- credits.rs
- cycle.rs
- details.rs
- features.rs
- gateway.rs
- gateway_tests.rs
- grants.rs
- invoices.rs
- keeper.rs
- lib.rs
- limits.rs
- margin.rs
- overages.rs
- platform.rs
- pricing.rs
- rename.rs
- report.rs
- requests.rs
- reset.rs
- retention.rs
- sales.rs
- statement.rs
- storage.rs
- stripe.rs
- stripe_sync.rs
- subscriptions.rs
- tax.rs
- tokens.rs
- webhooks.rs