3 ms·
Why are people on the issue thread reporting that this has broken their builds when the change hasn't been applied yet?
by jka 5y ago
Why are people on the issue thread reporting that this has broken their builds when the change hasn't been applied yet?
- jka 5y agoAha: it's because the project team merged this change that intentionally fails the build when people have pinned their workflows to use the deprecated branch name: https://github.com/google-github-actions/setup-gcloud/pull/537 https://github.com/google-github-actions/setup-gcloud/pull/5... (that makes sense; there has been a warning in place for a long time, and pinning to a name can be risky when the content within that reference may change over time)
- deleted 5y ago[deleted]
- TehShrike 5y agoIt does seem like a weird bug that this would cause errors https://github.com/estuary/flow/runs/5642694619?check_suite_focus=true#step:6:73 https://github.com/estuary/flow/runs/5642694619?check_suite_... seems like it should be some kind of warning instead of an error?