Skip to content

v0.1.2

Marketplace
Marketplace

Choose a tag to compare

View all tags
@skil-lock skil-lock released this 22 May 06:53
v0.1.2
6ec32f1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v0.1.2 — PR comment now renders cleanly

Bug-fix release. The Action's PR-comment step now posts the actual capability-delta markdown body instead of a literal file path. SARIF upload (the v0.1.1 feature) is unchanged and was verified live on a real PR (skills-lock/example-claude-code-skills#1).

Upgrade

- uses: skills-lock/skil-lock-action@v0.1.2
  with:
    pin-binary: v0.1.1
    sarif: true   # optional; requires security-events: write

pin-binary stays at v0.1.1 — the CLI binary itself did not change. Workflows currently using @v0.1.0 or @v0.1.1 should bump to @v0.1.2.

Notes

  • No breaking changes.
  • No new inputs.

Details (for the curious)

The PR-comment upsert step was passing gh api -f body=@$BODY, relying on a curl-style file-reference syntax that gh CLI does not implement. As a result, comments posted by v0.1.0 and v0.1.1 contained the literal string @/home/runner/work/_temp/skil-lock-pr-comment.md instead of the markdown body.

Fix: the body file is round-tripped through jq -Rs '{body: .}' and piped to gh api --input -. jq is preinstalled on the only platforms the composite supports.

Test coverage for the PR-comment path is tracked at #3.

Changes

  • #2 — fix: PR comment body posted as literal '@/path' instead of file contents
Assets 2
Loading