ci: foundation parity with dario / claude-bridge / deepdive#1
Merged
Conversation
Standard CI / security / release scaffolding, ported pattern-for-pattern: - ci.yml: typecheck + build + --help smoke on Node 20/22 - codeql.yml: javascript-typescript on PR + push + weekly scheduled - actionlint.yml: v1.7.1 on every PR + push (no path filter — required- check-never-reports trap lesson from sibling repos) - dependabot.yml: weekly npm + github-actions, non-major grouped - stale.yml: 60 warn + 14 close, exempts security/auth/review-feedback/ help-wanted/good-first-issue/pinned for issues; wip/blocked/security for PRs - auto-release.yml: fires on merged PR, version-bump gate, inline npm publish with SLSA provenance (GITHUB_TOKEN doesn't fire downstream workflows — deepdive v0.3.0 lesson baked in preemptively) Plus CHANGELOG.md with the Unreleased convention documented, and a seed-origin note in the [0.1.0] section pointing at agent@bef177d. No runtime-behavior change.
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.
Summary
Standard CI / security / release scaffolding, ported pattern-for-pattern from the sibling askalf repos. No runtime-behavior change — this is just the boring necessary plumbing before any code work starts.
Lessons from the sibling repos baked in preemptively:
GITHUB_TOKEN-created releases don't fire downstream workflows (loop protection). Cost deepdive v0.3.0 a manual delete+recreate. Publish logic lives directly in `auto-release.yml` so the chain is single-run.What's here
Follow-up (not in this PR, tracked for after merge)
Test plan