Watch dependencies — this repo had nothing watching them - #4
Merged
Conversation
Deploy automation was deferred so a human could watch the first-ever
deploy of new infrastructure, with a note to automate once phase 1 was
stable. Phase 1 is stable, and leaving it deferred turned out worse than
what it avoided: fly.toml only took effect if someone remembered to run
`fly deploy` by hand.
That failed silently on 2026-09-09. A scale-to-zero change merged with
CI fully green and never reached Fly — the app kept running always-on,
and the config looked applied because the commit was on master. It was
only caught by checking the machine state directly. Config that silently
doesn't apply is more dangerous than no config, because it reads as done.
Deploy runs on push to master only, after BOTH matrix legs (sqlite and
postgres) pass — this service runs one codebase against either dialect,
so a green sqlite leg alone is not evidence a deploy is safe.
Two flags, each for a concrete reason:
--strategy immediate this app mounts sentinel_license_data, and the
default rolling strategy stands up a parallel
machine first, which errors on the volume's
single attachment slot.
--ha=false Fly otherwise provisions two machines. It did
exactly that on the manual deploy of the sibling
Sync service and the extra had to be scaled away
by hand; the volume could not serve two anyway.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
No Dependabot config existed here. That is the same gap that produced the Sentinel AI agent's three production breakages in two days: mcp 2.x renaming a symbol, Starlette removing on_startup, and a ceiling added to stop the second one silently pinning the service to a Starlette line carrying 7 advisories. All three surfaced on a rebuild of a repo nobody had rebuilt since June. `pip-audit --strict` in CI catches a known advisory against what is already pinned. It does nothing about a lockfile quietly ageing out of support, which is the failure that actually happened. No auto-merge workflow, deliberately. This repo now deploys to Fly on push to master, and GitHub does not trigger `on: push` workflows for commits pushed with GITHUB_TOKEN — so an auto-merge would land a bump on master WITHOUT deploying it, and nothing would report an error. That is an observed bug in Sentinel-Command, where four frontend bumps merged and never shipped. A human merge triggers the deploy normally. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dependabot config only — no code, no CI changes.
This repo had nothing watching its dependencies. That's the same gap that produced the Sentinel AI agent's three production breakages in two days (mcp 2.x renaming a symbol, Starlette removing
on_startup, and a ceiling added to stop the second one silently pinning the service to a Starlette line with 7 advisories) — all three surfaced on a rebuild of a repo nobody had rebuilt since June.The audit step in CI catches a known advisory against what's already pinned. It does nothing about a lockfile quietly ageing out of support, which is the failure that actually happened.
No auto-merge workflow, deliberately. This repo now deploys to Fly on push to master, and GitHub doesn't trigger
on: pushworkflows forGITHUB_TOKENmerges — so an auto-merge would land a bump on master without deploying it, with nothing reporting an error. That's an observed bug in Sentinel-Command, where four frontend bumps merged and never shipped. A human merge triggers the deploy normally.Verified each declared
directoryactually contains a manifest — a wrong path makes Dependabot silently do nothing, which is the same class of failure this is meant to close.🤖 Generated with Claude Code