Skip to content

ci: backport sync-agent-instructions.yml and dependabot.yml to main - #627

Open
tvna wants to merge 1 commit into
mainfrom
claude/release-process-bug-analysis-bl5zsu
Open

ci: backport sync-agent-instructions.yml and dependabot.yml to main#627
tvna wants to merge 1 commit into
mainfrom
claude/release-process-bug-analysis-bl5zsu

Conversation

@tvna

@tvna tvna commented Jul 31, 2026

Copy link
Copy Markdown
Owner

Summary

Why

Root-cause analysis of a release-process bug found this repo's actual GitHub default branch is develop, and GitHub Actions resolves schedule triggers (and default-ref workflow_dispatch runs) from the workflow YAML on the default branch. develop's stale release.yml has been running its weekly schedule and silently no-op'ing (green success, nothing published) since the release-fix chain (#521/#523/#525/#526/#527) landed on main only.

The owner has decided to switch GitHub's default branch from develop to main. Before that flip, sync-agent-instructions.yml and dependabot.yml need to be at parity on main, or the flip silently regresses them the same way it was silently breaking release.yml:

This PR closes that gap so the default-branch switch (tracked as a follow-up owner action — no API/MCP tool exists to change it programmatically) is safe.

Verification

  • actionlint .github/workflows/sync-agent-instructions.yml — exit 0, no findings.
  • .github/dependabot.yml — parsed with PyYAML, confirmed all 3 ecosystems (github-actions, uv, devcontainers) and target-branch: develop.
  • Confirmed both files are byte-identical to develop's current copies.
  • No existing test reads either file's content (checked tests/workflow/test_release_management.py, the only .github-content test on either branch), so none needed updating.

Non-goals

Closes #626
Refs #518


Generated by Claude Code

Bring main's copies to parity with develop's current content ahead of
the GitHub default-branch switch to main.

sync-agent-instructions.yml finishes #518, which retargeted the
sync-claude-md/sync-apm-skills jobs at develop (explicit ref: develop
checkout, base: develop) and added a sync-rulesets job, but only ever
landed on develop's copy. GitHub Actions resolves schedule/default-ref
workflow_dispatch triggers from the default branch's copy of the
workflow file, so main's stale pre-#518 copy (base: main, no explicit
ref) would otherwise run once main becomes the default branch.

dependabot.yml drops the stale pre-bun-migration npm ecosystem entry
(package-lock.json no longer exists, #353) and switches the Python
ecosystem from pip to uv, matching develop. GitHub reads dependabot
config from the default branch, so this would otherwise regress the
moment main becomes default.

release.yml needs no change: main's copy already has the fixed daily
cadence, --no-ci, and develop-derived commit prep from #521-#527.

Refs #626, #518
@vercel

vercel Bot commented Jul 31, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
command-ghostwriter Error Error Jul 31, 2026 11:29pm

@github-actions

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails
actions/actions/checkout 3d3c42e5aac5ba805825da76410c181273ba90b1 🟢 6.9
Details
CheckScoreReason
Binary-Artifacts🟢 10no binaries found in the repo
Code-Review🟢 10all changesets reviewed
Maintained🟢 1025 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing⚠️ 0project is not fuzzed
Pinned-Dependencies🟢 3dependency not pinned by hash detected -- score normalized to 3
License🟢 10license file detected
Packaging⚠️ -1packaging workflow not detected
Signed-Releases⚠️ -1no releases found
Security-Policy🟢 9security policy file detected
Branch-Protection🟢 5branch protection is not maximal on development and all release branches
SAST🟢 10SAST tool is run on all commits
actions/step-security/harden-runner bf7454d06d71f1098171f2acdf0cd4708d7b5920 🟢 7.9
Details
CheckScoreReason
Binary-Artifacts🟢 10no binaries found in the repo
Branch-Protection🟢 8branch protection is not maximal on development and all release branches
CI-Tests🟢 1013 out of 13 merged PRs checked by a CI test -- score normalized to 10
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Code-Review🟢 10all changesets reviewed
Contributors🟢 6project has 2 contributing companies or organizations -- score normalized to 6
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Dependency-Update-Tool🟢 10update tool detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Maintained🟢 1020 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Packaging⚠️ -1packaging workflow not detected
Pinned-Dependencies🟢 6dependency not pinned by hash detected -- score normalized to 6
SAST🟢 10SAST tool is run on all commits
Security-Policy🟢 10security policy file detected
Signed-Releases⚠️ -1no releases found
Token-Permissions🟢 10GitHub workflow tokens follow principle of least privilege
Vulnerabilities⚠️ 016 existing vulnerabilities detected

Scanned Files

  • .github/workflows/sync-agent-instructions.yml

tvna commented Aug 1, 2026

Copy link
Copy Markdown
Owner Author

The Vercel deployment check is failing, but it's pre-existing and unrelated to this PR: this PR only touches .github/workflows/sync-agent-instructions.yml and .github/dependabot.yml (no web-app code). PR #527 — which also touched no web-app code — hit the identical Deployment has failed Vercel status and still merged cleanly into main. It isn't one of the required status checks (test-and-build / Workflow summary [Test & Build (on pull request)] is the only one, and it's green here). Not treating it as blocking or in scope for this PR; flagging for visibility only.


Generated by Claude Code

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.

2 participants