docs: npm publishing runbook + placeholder record - #11
Closed
ihistand wants to merge 1 commit into
Closed
Conversation
Records what's already on the npm registry under the sqlanvil org and how real packages will be published once Phase 3b/4 land. Captures: - npm org sqlanvil (free, public, created 2026-05-27) - Published placeholders: @sqlanvil/cli@0.0.1, @sqlanvil/core@0.0.1 (name reservations only — print "not yet published" and exit 1) - Names to consider claiming later (postgres, supabase, protos, unscoped sqlanvil) — avoid speculative grabs (npm anti-squatting) - Real-publish workflow via Bazel tarball + docker cp - Version policy (0.0.x placeholders, 0.x.y pre-release, 1.0.0 stable) - Future CI automation snippet - 2FA + granular access token guidance Placeholder package sources themselves were not committed — they were one-shot scaffolds outside the repo. This doc is the audit trail.
Collaborator
Author
|
Superseded: the Postgres reintegration + Dataform→SQLAnvil rename landed on |
ihistand
added a commit
that referenced
this pull request
Jul 21, 2026
…a post_operations) Mirrors the agent-skills SKILL.md update: delta #10 expanded with the AI/BI framing (descriptions/columns persist as catalog comments, join targets named in column descriptions, PK/FK via post_operations with NOT ENFORCED on BigQuery targets, uniqueKey/uniqueKeys exclusivity, catalog artifacts, guide link); delta #9 covers FKs; delta #11 NOT-ENFORCED flag scoped. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W86VUf4ptKnmhxWoqgA7gb
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
Records what's already published on the npm registry under the `sqlanvil` org + how real packages will be built and published once Phase 3b/4 land.
Already on npm
Both placeholders print "not yet published" and exit non-zero. Source files were one-shot scaffolds outside the repo (now deleted) — this doc is the audit trail.
Contents
Independent of code stack
Planning doc only, no code changes. Can merge any time; doesn't block the postgres-first-class PR stack, docs site plan, or branch strategy PRs.
Test plan
🤖 Generated with Claude Code