| name | sdk-sync |
| description | Keep shared configuration, community files, and CI templates consistent across all SDK repositories. Use when auditing cross-repo consistency or propagating a change (license, contributing guidelines, CI updates, bot config) to multiple SDK repos. |
SDK Sync
Audit and synchronize shared files across all Altertable SDK repositories. Repository inventory: repositories.config.json. Edit that file to add/remove repos — all scripts pick it up automatically.
Rules: change-control · contribution · safety
Managed Files and File Templates
All files in the templates/ folder are the source of truth and must be copied into every target repo, mirroring the same directory structure. Files containing {variable} placeholders are templated; all others are copied verbatim.
Managed files include community docs, issue/PR templates, funding metadata, and release automation guardrails. Language-specific CI workflows are owned by each SDK repo, but the semantic PR title workflow is shared because release-please depends on squash-merge titles.
Template variables
Templated files contain {variable} placeholders. Render them with repo-specific values during sync:
| Variable | Source |
|---|
{package_name} | From sdk-release naming conventions |
{package_type} | Registry type: node, python, ruby, rust, java, kotlin, go, php, swift |
{language} | Target language name |
{language_version} | Minimum required version (e.g., 3.1, 18, 1.21) |
{language_setup_action} | GitHub Actions setup action (e.g., actions/setup-node@v4, actions/setup-python@v5) |
{language_version_key} | Setup action version key (node-version, python-version, ruby-version, etc.) |
{install_command} | Repo's existing toolchain |
{test_command} | Repo's existing toolchain |
{check_command} | Repo's existing toolchain |
{linter} | Repo's existing toolchain |
{formatter} | Repo's existing toolchain |
{lint_command} | Repo's existing toolchain |
Sync Workflow
Phase 1: Audit
- Read
repositories.config.json and iterate over the sdks array (do not include the workspace entry).
- Clone or fetch all SDK repos from the
sdks array.
- For each managed file, compare the repo's version against the source of truth.
- Treat a missing
.github/workflows/semantic-pr.yml as release automation drift for every repo that uses release-please.
- Report drift:
DRIFT REPORT
============
altertable-lakehouse-ruby:
✗ SECURITY.md — missing
✗ CONTRIBUTING.md — outdated (missing Conventional Commits section)
✗ .github/workflows/semantic-pr.yml — missing
✓ LICENSE — ok
altertable-py:
✓ SECURITY.md — ok
✗ .github/ISSUE_TEMPLATE/bug_report.yml — missing
✓ LICENSE — ok
Phase 2: Generate patches
For each repo with drift:
- Copy verbatim files from
templates/ directly.
- Render templated files from
templates/ with repo-specific variables (see Template variables above).
Phase 3: Open PRs
For each repo with changes:
- Create a branch:
chore/sync-community-files
- Commit all changes:
chore: sync community files
- Open a PR with the drift report as the body
Adding a New Managed File
When a new file should be consistent across all SDK repos:
- Add the file to the
templates/ folder at the path it should occupy in the target repo.
- If it needs per-repo values, use
{variable} placeholders and add a row to the Template variables table above.
- Run the sync workflow to propagate.
Acceptance Checklist
