Skip to content

Conversation

@LukeMathWalker
Copy link
Owner

The check used to be run on installation, but this causes issues with CI caching: if the binary is restored from a cache in a new runner, the environment hasn't gone through the setup but the flow won't trigger since the binary is already where we expect it to be.

We now run the setup flow unconditionally.

Fixes #474

The check used to be run on installation, but this causes issues
with CI caching: if the binary is restored from a cache in a new runner,
the environment hasn't gone through the setup but the flow won't
trigger since the binary is already where we expect it to be.

We now run the setup flow unconditionally.
@LukeMathWalker
Copy link
Owner Author

/ok-to-test sha=7121ae0

@LukeMathWalker LukeMathWalker merged commit 9826331 into main Mar 22, 2025
10 checks passed
@LukeMathWalker LukeMathWalker deleted the fix-freshness-starter branch March 22, 2025 15:51
@pavex-releaser pavex-releaser bot mentioned this pull request Mar 22, 2025
@pavex-releaser pavex-releaser bot mentioned this pull request Jul 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The github workflow Freshness fails in the starter project

2 participants