ci(release): version packages - #467
Merged
Merged
Conversation
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@0.29.0
Minor Changes
cd881a1Thanks @eXamadeus! - BREAKING (pre-1.0 minor): activate supplementary-file support, archive and lockfile format0.2, and adapter API0.1.Every
facet buildnow emitsfacetVersion: 0.2with a complete per-entry hash map. Facets can explicitly declare opaque supplementary files: skill companions install and remove atomically with their owning skill, while root and other archive-only files remain integrity-protected without being materialized. Valid legacy0.1archives remain installable during the compatibility window.Current lockfiles and machine-local receipts use format
0.2with canonical per-file integrity and ownership records, enabling exact-path drift reporting, repair, rollback, and offline removal without deleting unowned files.facet createwrites and declares an editableREADME.mdby default, with--no-readmeas the headless opt-out.facet editmanages bothREADME.mdand the extensionlessREADMEand reconciles supplementary declarations transactionally.New manifests require single-segment Agent Skills names, and skills and commands cannot share a name. Existing published
0.1archives retain legacy naming behavior, but affected source manifests must be renamed before rebuilding as0.2.This CLI supports only the tagged adapter API
0.1. Positional0.0adapters fail closed before contract calls or project mutation with reinstall guidance. Rebuild custom adapters against the current@agent-facets/adapterSDK and reinstall incompatible adapters before continuing.Note
Low Risk
Mechanical release/versioning changes only; behavioral risk is in the already-merged feature documented in the changelog, not in this diff.
Overview
Release packaging only: bumps
agent-facets(and lockfile entries) from 0.28.0 → 0.29.0, appends the 0.29.0 section topackages/cli/CHANGELOG.md, and removes the consumed changeset.changeset/activate-supplementary-files.md.The changelog entry documents the pre-1.0 breaking minor shipped via #462: archive/lockfile format 0.2, supplementary files, default
README.mdonfacet create, stricter Agent Skills naming, and adapter API 0.1 with fail-closed 0.0 adapters—not new implementation in this diff.Reviewed by Cursor Bugbot for commit 63897e5. Bugbot is set up for automated code reviews on this repo. Configure here.