Skip to content

Conversation

@marcusthelin
Copy link

When the wait option was introduced, it was set to true as default. The way this flag works in the gcloud CLI is that it will execute the job and then wait for it to succeed. This is a major change in the action's behavior, and should be opt-in.

Fixes #578

@bpingris
Copy link

bpingris commented Sep 3, 2025

wait: (Optional, default: true) If true, the action will wait for the job to complete before exiting. This option only applies to jobs.

there is also this part in the README where you could change the default: true to false

google-github-actions-bot pushed a commit that referenced this pull request Sep 3, 2025
This was an unintentional breaking change, but we didn't catch it
because GitHub changed how floating tags work.

- Closes
#578
- Closes
#579
@marcusthelin marcusthelin deleted the make-wait-default-false branch September 4, 2025 11:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

v2.7.5 triggers automatic execution of jobs after deployment

2 participants