This repository was archived by the owner on Aug 19, 2026. It is now read-only.
Add public package boundary - #3
Merged
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Adds the public Summon package boundary on top of the clean source import:
@summon-internal/*@anarchitecture/summon,@anarchitecture/summon-server,@anarchitecture/summon-reactdistoutput with import rewriting, without committing generateddistSUMMON_NPM_PUBLISH_TOKENValidation
pnpm install --frozen-lockfilepnpm typecheckpnpm testpnpm buildpnpm check:public-packagespnpm pack:dry-runpnpm smoke:public-packagespnpm test:safetygit diff --cached --check@summon/*, public dist@summon-internal/*leaks, stalesourceMappingURL, obvious secrets, and accidental generated filesNotes
The first publish can happen after this merges if
SUMMON_NPM_PUBLISH_TOKENis configured. The public package manifests use semver dependencies (^0.1.0) rather than workspace protocols so packed/published manifests are consumer-safe.