Releases: agent-facets/facets
Releases · agent-facets/facets
Release list
agent-facets@0.22.2
Immutable
release. Only release title and notes can be modified.
Patch Changes
- #373
0da8ff6Thanks @eXamadeus! - This fixes a bug withfacet editwhere configuration values outside the description and name were stripped for assets.
They now should survivefacet editcorrectly
agent-facets@0.22.1
Immutable
release. Only release title and notes can be modified.
@agent-facets/adapter-codex@0.4.0
Immutable
release. Only release title and notes can be modified.
agent-facets@0.22.0
Immutable
release. Only release title and notes can be modified.
Minor Changes
- #353
5d78611Thanks @eXamadeus! - Add in private facet support
@agent-facets/protocol@0.22.0
Immutable
release. Only release title and notes can be modified.
Minor Changes
- #353
5d78611Thanks @eXamadeus! - Add in private facet support
@agent-facets/adapter-opencode@0.6.0
Immutable
release. Only release title and notes can be modified.
Minor Changes
- #348
c4ac343Thanks @eXamadeus! - Expand metadata support to include model, permission, agent, and subtask fields
agent-facets@0.21.1
Immutable
release. Only release title and notes can be modified.
Patch Changes
- #342
3314057Thanks @eXamadeus! - Add in registry URL tofacet whoami
agent-facets@0.21.0
Immutable
release. Only release title and notes can be modified.
Minor Changes
- #338
b663d3cThanks @eXamadeus! - TightenparseSlugto 2-64 chars, reject consecutive hyphens, and refresh manifest spec docs to document canonical facet-name grammar
Patch Changes
- #334
c44c321Thanks @eXamadeus! - Route scoped facet publish, resolve, and download through two-segment{scope}/{name}registry paths to avoid%2F-encoding rejection - #335
2861755Thanks @eXamadeus! - FixwriteBuildOutputto create parent directories for scoped (@scope/name) and slash-containing archive paths, and accept scoped facet names in create/edit views
@agent-facets/protocol@0.21.0
Immutable
release. Only release title and notes can be modified.
Minor Changes
- #338
b663d3cThanks @eXamadeus! - TightenparseSlugto 2-64 chars, reject consecutive hyphens, and refresh manifest spec docs to document canonical facet-name grammar
@agent-facets/protocol@0.20.0
Immutable
release. Only release title and notes can be modified.
Minor Changes
- #331
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.