.github/workflows: clarify tailcat breakage check is only a heads-up

Rename the tailcat job added in 6c06e00ad to
heads-up-hypothetical-tailcat-build-using-this-commit and print an
explanation on failure: the job builds tailcat against tailscale.com at
this commit rather than the version tailcat pins, so a failure doesn't
break tailcat until it bumps its dependency. It only matters if the API
or behavior breakage is unexpected. People were misreading failures as
something more urgent.

Updates tailscale/corp#24454

Signed-off-by: Brad Fitzpatrick <[email protected]>
Change-Id: I3f8a1c92d47e60b5a2e9c14f7d08b361
This commit is contained in:
Brad Fitzpatrick authored and Brad Fitzpatrick committed 2026-09-04 09:28:17 -07:00
1 parent 33cc45a32a
commit b62350fbec
1 file changed
+18
+18
View File
@@ -23,6 +23,7 @@ concurrency:
jobs:
tailcat:
name: heads-up-hypothetical-tailcat-build-using-this-commit
runs-on: ubuntu-latest
steps:
- name: Check out tailscale
@@ -45,3 +46,20 @@ jobs:
- name: Run tailcat tests
working-directory: tailcat
run: ../tailscale/tool/go test ./...
- name: Explain failure
if: failure()
run: |
cat <<'EOF' | tee -a "$GITHUB_STEP_SUMMARY"
Don't panic!
This job builds the tailscale/tailcat repo against the tailscale.com
module at this commit, not the version tailcat actually pins in its
go.mod. A failure here does NOT break tailcat today; nothing breaks
until tailcat bumps its tailscale.com dependency to include this
change.
This is only an early heads-up. Be concerned only if this API or
behavior breakage is unexpected. If the breakage is intentional,
proceed and coordinate a matching tailcat update.
EOF