Skip to content

chore: retire upstream-sync cron, sync manifest to 2.1.161#40

Merged
arzafran merged 1 commit into
mainfrom
chore/retire-upstream-sync-cron
Jun 3, 2026
Merged

chore: retire upstream-sync cron, sync manifest to 2.1.161#40
arzafran merged 1 commit into
mainfrom
chore/retire-upstream-sync-cron

Conversation

@arzafran
Copy link
Copy Markdown
Member

@arzafran arzafran commented Jun 3, 2026

Summary

Replaces #39 (closed). The daily upstream-sync cron is retired in favor of the manual /cc sync skill.

Why: the bot could only ever bump a version number and dump the drift string into a PR body. Its diffSets compares the manifest against cc-settings' own zod schema — never upstream — and it never fetched the changelog, so it was structurally blind to new features, settings keys, env vars, hook events, and dedupe opportunities. That triage is the human skill's job. The bot's PRs looked actionable but weren't, and raced the manual flow (#39 had already bumped the manifest while a manual sync was mid-flight). Making the cron smarter would have required a standing ANTHROPIC_API_KEY/OAuth token in repo secrets, burned unattended on every release.

Removed

  • .github/workflows/upstream-sync.yml (the cron)
  • openSyncPr / saveManifest / the --open-pr branch in src/upstream/scan.ts — now a pure dry-run detector (no writeFile/runProcessFull imports)
  • stale "daily GH Action" / "bot owns this file" references in the manifest description/source, skills/cc/SKILL.md, src/schemas/skill.ts, and the ci.yml upstream-scan comment

Kept

  • bun run upstream:scan — the dry-run detector, now the manual way to spot drift before running /cc sync
  • its non-gating upstream-scan CI job (surfaces drift in PR logs)

Also: upstream sync to Claude Code 2.1.161

Manifest 2.1.1602.1.161. Release is otherwise all bug fixes / UI / perf with no cc-settings surface. One tracked addition: CLAUDE_CODE_TMPDIR (surfaced by the EADDRINUSE/Unix-socket fix) → knownEnvVars + env-var table. OTEL_RESOURCE_ATTRIBUTES skipped (generic OTEL SDK var, outside our CC-specific convention).

Test Plan

  • bun run typecheck clean
  • bun test — 467 pass, 0 fail
  • bun run lint clean
  • bun run lint:skills — 0 errors/warnings
  • bun run upstream:scan — no drift detected at 2.1.161

The daily upstream-sync GitHub Action could only bump a version number and dump the drift string into a PR body — it never read the changelog, so it was blind to new features, settings keys, env vars, hook events, and dedupe opportunities (its diffSets compares the manifest against our own zod schema, not upstream). That triage is the human /cc sync skill's job; the bot's PRs looked actionable but weren't and raced the manual flow. Making it smarter would have meant a standing ANTHROPIC_API_KEY/OAuth token in CI secrets, billed unattended on every release.

Removed: the workflow, the --open-pr path + openSyncPr/saveManifest in scan.ts (now a pure dry-run detector), and stale 'daily GH Action'/'bot owns this file' references across the manifest, skill, schema, and CI comment. Kept: bun run upstream:scan (dry-run detector) + its non-gating CI job.

Also syncs the manifest to Claude Code 2.1.161 (otherwise all bug fixes; adds CLAUDE_CODE_TMPDIR to knownEnvVars + the env-var table; OTEL_RESOURCE_ATTRIBUTES skipped as a generic OTEL var).
@arzafran arzafran merged commit fff29b0 into main Jun 3, 2026
13 checks passed
@arzafran arzafran deleted the chore/retire-upstream-sync-cron branch June 3, 2026 15:07
@arzafran arzafran mentioned this pull request Jun 3, 2026
4 tasks
arzafran added a commit that referenced this pull request Jun 3, 2026
Versions work that had accumulated in [Unreleased] without a bump: team-knowledge repo migration (#38), nuclear-review maintainability pass, upstream-sync cron retirement + CC 2.1.161 sync (#40), dynamic-workflow guidance + dead-telemetry removal (#41), docs accuracy pass + USAGE.md removal (#42).

VERSION 11.16.0 → 11.17.0; CHANGELOG [Unreleased] promoted to [11.17.0].
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant