Skip to content

chore(template-sync): bootstrap sync state and sync to template-base v1.15.2 - #3

Merged
crazyracer98 merged 2 commits into
mainfrom
wip/OF1
Nov 13, 2026
Merged

crazyracer98 merged 2 commits into
mainfrom
wip/OF1

Conversation

@crazyracer98

Copy link
Copy Markdown
Contributor

Bootstraps .github/template-sync-state.json (the weekly sync was a silent no-op: no state file) and syncs from v1.1.0 to template-base v1.15.2, applying the replace and merge tiers exactly as template_sync.py apply does (no conflicts).

Decisions: the repo was byte-identical to v1.1.0 in replace-tier paths, so v1.1.0 is the bootstrap tag. Instance-owned and untouched: profile/, brand/ (local manifest ignore), README.md. By hand: removed root Dockerfile and .dockerignore (moved to .devcontainer/ upstream; sync only deletes paths the new manifest matches); replaced the no-op Makefile with the v1.15.2 release contract (new targets required by release.yml and its tests).

CI now runs zizmor, gitleaks (history) and osv-scanner (skipped: no lockfile). Not merged: awaiting review.

…v1.15.2

- Seed .github/template-sync-state.json (v1.1.0), then apply replace/merge tiers to v1.15.2 and record it
- Adds zizmor, gitleaks and osv-scanner hooks plus the split fix/apply moderate workflows
- Drop root Dockerfile/.dockerignore (moved to .devcontainer/); adopt the new Makefile release contract
- Keep instance-owned profile/ and brand/ (local manifest ignore)
…he synced devcontainer.json references

- Ignore-tier file, never created by sync; copied from template-base v1.15.2
@crazyracer98
crazyracer98 merged commit bac571f into main Nov 13, 2026
4 checks passed
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