Conversation
Core and ui were already separate packages that never import each other; this locks that in. core/ becomes @based/core at the app version, published from the release tag. New ci.yml runs each project on its own plus tests, boundaries and the private guard. The paid product lives in a sibling repo and can never land here: gitignore, a tracked pre-commit hook, and a CI job all refuse its paths. BASED-PKG-BOUNDARIES, BASED-PRIVATE-GUARD, BASED-CORE-PUBLISH; BASED-RELEASE-CI gains the publish job. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Publishes under the npm org we already own instead of an unverified scope. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
What
Phase 1 of the based.ai roadmap (plan:
specs/based/plans/project-split.md). Two repos, three buildable projects: core and ui stay here as the packages they already are; the paid product lives in a sibling private repo and consumes@based/corefrom npm.core/becomes publishable as@based/coreat the app version.bump-version.ps1rewrites its manifest with the other three version sites;release.ymlgains apublish-corejob that refuses a mismatched tag.scripts/check-boundaries.tsfails if core and ui ever import each other (they don't today; this locks it in). The shell may import core.scripts/check-private.tsrefusesbased-ai/,paid/,private/,*.private/, env files and private keys. Runs as the tracked pre-commit hook in.githooks/and as a CI job againstgit ls-files.ci.ymlon push and PR: one job per project plus tests, boundaries, private guard. There was no push CI before.Spec
New: BASED-PKG-BOUNDARIES (unit), BASED-PRIVATE-GUARD (unit), BASED-CORE-PUBLISH (manual). Modified: BASED-RELEASE-CI.
Verified
bun test681 pass / 73 skip / 0 failbun run checkgreen; pre-commit hook ran on this branch's commitCyronius/based-aiboots a linked core and gets 200 from/api/healthBefore the next release tag
@basednpm scope withnpm publish --dry-runfromcore/; fall back to@cyronius/based-coreif takenNPM_TOKENrepo secret🤖 Generated with Claude Code