ci(release): version packages#332
Merged
Merged
Conversation
the-faceter
Bot
force-pushed
the
changeset-release/main
branch
from
fe9e632 to
089c573
Compare
Member
Merge activity
|
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.
This PR was auto-generated by the release workflow. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@agent-facets/protocol@0.20.0
Minor Changes
644f53bThanks @eXamadeus! - Add a facet identity grammar to the public API and enforce it inFacetManifestSchema.New exports:
parseFacetName,parseSlug, andvalidateFacetName, along with theFacetName,FacetNameResult, andSlugResulttypes. A facet identity is either an unscoped slug (cowsay) or a scoped@scope/name(@julian/cowsay), where every segment is a lowercase kebab slug. The parsers return discriminated-union results instead of throwing, andparseSlugis exported on its own so other facet-spec implementations (e.g. a registry enforcing scope ownership) validate scopes with the exact same grammar.FacetManifestSchemanow validates the manifestnamefield against this grammar. This tightens the previousname: stringbehavior: malformed facet identities (uppercase, leading/trailing hyphens, traversal segments, extra path depth, missing slash after@scope, etc.) now fail at manifest validation instead of deferring failure to build, publish, or install. Asset names remain governed separately byvalidateAssetName— asset names stay local path-safe identifiers while facet identities may carry a registry scope.