Skip to content

v0.6.1

Choose a tag to compare

@SanderMuller SanderMuller released this 19 Apr 12:49
· 43 commits to main since this release
Immutable release. Only release title and notes can be modified.
66c3750

Package Boost v0.6.1

Documentation-only release. Pins the --format=json schema-v1
contract ahead of the first downstream CI integration (landing in
laravel-fluent-validation v1.13) — locks the shape so future
consumers don't have to guess what fields mean or hit the same
mcp-as-array foot-gun as the pre-integration peer review caught.

Fixes

Schema docstring pinned

Three fields that were underspecified in 0.6.0's README now have
explicit semantics:

  • hint is advisory prose, not a command-to-run. For skills
    on updated actions: "symlink → <relative target>". For
    guidelines on updated / new: "+N lines" / "-N lines" /
    "content updated". No hint on removed or unchanged. The
    fix for any drift is always package-boost:sync without
    --check — don't templatize hint as auto-fix output.
  • line_delta (guidelines only) is scoped to the
    <package-boost-guidelines> block. Since sync only rewrites that
    block, it's effectively the synced-region delta; everything else
    in the target file is never touched. Don't read it as a full-file
    delta.
  • mcp is a single { action, target } object, never an
    array. The previous jq example in the README only drained
    collection-shaped categories; it would have silently missed MCP
    drift.

Expanded CI example

Replaced the two-branch jq snippet with a complete one that drains
all six collection arrays (skills × { new, updated, removed },
guidelines × same) plus the MCP object branch via direct
equality on action:

jq -r '
    (.skills.new, .skills.updated, .skills.removed)[]?.target,
    (.guidelines.new, .guidelines.updated, .guidelines.removed)[]?.target,
    if .mcp.action == "new" or .mcp.action == "updated" then .mcp.target else empty end
' | sort -u | sed "s|^|  - |"

Upgrading

No code changes. Documentation only. Text and JSON output are
byte-compatible with 0.6.0.

Compatibility

No breaking changes. Schema v1 contract unchanged — this release
just documents what 0.6.0 already returned.