You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sync.sh now never blocks commits on network failure:
- SYNC_OFFLINE=1 env var → skip entirely with warning, exit 0
- curl fetch failures → warn to stderr, skip that file, exit 0
- missing curl/jq → warn + exit 0 (local dev without deps still commits)
- unknown language → warn + exit 0 (no more hard die)
- committed files: write to .tmp first, atomically mv on success, preserving
cached copy if fetch fails mid-run
- --max-time 10 on every curl so a hung network doesn't stall the hook
Committed files stay committed (release-please-config.json must live at repo
root for release-please-action to read it in CI); cached files stay in
.shared/ as before. Offline tolerance is purely about hook robustness — CI
still re-fetches on every run so canonical drift is picked up.
Consumers' pre-commit entry bootstrap will be updated in a follow-up to
tolerate the initial curl (before .shared/sync.sh is cached).
0 commit comments