Publish the CRX from a timer, and refuse an unbumped version

Mirrors the autotrader stack's auto-deploy: fetch every minute, act when master
moves, lock against overlap, rewrite .last-check every run so a silent failure
is visible. Only extension/ and deploy/ changes publish - repacking for a docs
edit would republish an identical CRX every minute.

The guard is the part that earns its place. Chrome ignores a CRX that is not
strictly newer, so shipping extension changes without bumping manifest.json is
a no-op that looks exactly like success until someone notices the fix never
arrived. That now fails loudly instead.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

This commit is contained in:

Brandon Li

2026-08-31 16:10:21 -05:00

co-authored by

Claude Opus 5

parent 56114b727c

commit 95c073d4c2

6 changed files with 171 additions and 3 deletions

.gitignore

View File

@@ -66,3 +66,8 @@ scripts/.last-check
 # The deploy template is meant to be read, unlike a real .env
 !deploy/.env.example
 # publish bookkeeping
 deploy/publish.log
 deploy/.last-check
 deploy/.publish.lock