Skip to content

Multi-tier framework for evaluating AI agent skills and plugins with quality gates, security scanning, harness compatibility checks, semantic overlap detection, synthetic evaluation dataset generation, and live agent evaluation that measures how skills affect agent behavior. Ships reusable CI templates that bring every check to any repository.

chore(release): prepare v0.6.0 (#216)

Narendran Raghavan5cf7684624ec
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 3b357dbc..82207bbf 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,8 @@ All notable changes to SkillEvaluator are documented in this file.
## Unreleased
+## 0.6.0 - 2026-10-20
+
### Added
- Optional `skillevaluator dashboard` tables for comparing saved Tier 3 reports
@@ -251,6 +253,49 @@ All notable changes to SkillEvaluator are documented in this file.
display metadata, Markdown structure injection, and inline-JavaScript
injection through untrusted agent or skill names.
+### Security
+
+- The docs-publishing workflow, the only one that passes a secret to a step,
+ now pins `actions/checkout` to a commit SHA, declares
+ `permissions: contents: read`, and sets `persist-credentials: false`.
+ `dco.yml` no longer persists checkout credentials either.
+- Docs are now published with the same Fern CLI version they are validated
+ with. Both workflows install the CLI from `fern/package.json` and its
+ committed lockfile; a test checks that the pin matches `fern/fern.config.json`.
+- Workflow hardening guards now glob `.github/workflows/` instead of a
+ hardcoded two-file list, so every workflow — including any added later — must
+ pin each action to a commit, avoid persisting checkout credentials, and
+ declare a `permissions:` block. The guards also cover job-level
+ `permissions:` overrides and job-level reusable-workflow `uses:` references,
+ neither of which the step-level checks reached.
+- The Fern CLI is now installed from a committed lockfile, `fern/package-lock.json`,
+ with `npm ci --prefix fern --ignore-scripts --omit=optional`, and both workflows
+ invoke `./fern/node_modules/.bin/fern` rather than a binary on `PATH`. Previously
+ `publish-docs.yml` ran `npm install`, which re-resolves every transitive
+ dependency from semver ranges on each run: pinning `fern-api`'s own version
+ pinned nothing beneath it. `@scarf/scarf` — reached through `fern-api`'s
+ optional dependency on `@boundaryml/baml` — declares a `postinstall` script.
+ The install step did not receive `FERN_TOKEN`, but its resulting CLI was later
+ run in the token-bearing publish step. The lockfile pins every package to an
+ exact version and integrity hash, `--ignore-scripts` stops lifecycle code
+ running, and `--omit=optional` (which npm honours for this local install, but
+ silently ignores for a `--global` one) leaves `fern-api` alone in the tree.
+ Guards now permit only the reviewed lockfile install command in workflows,
+ check the Fern manifest and lockfile dependency inputs, and require
+ `fern/package.json`, `fern/package-lock.json`, and `fern/fern.config.json` to
+ name the same CLI version. Fern dependency and config changes run the full
+ CI lane, including dependency review, while `fern check` runs in both lanes.
+ The developer-facing install instructions
+ (`docs/README.md`, `docs/AGENTS.md`, `docs/developer-guide.mdx`) use the same
+ lockfile install, so a contributor or agent following them gets the tree CI runs.
+- The action-pinning guard now accepts a same-repo composite action or
+ reusable workflow (`uses: ./...`) without requiring a commit SHA, since
+ GitHub always resolves a local reference from the caller's own commit and
+ nothing about it can float. A local reference that escapes the repository
+ (e.g. `./../outside`) or carries an `@ref` (a syntax local references don't
+ have) is still rejected, and a `docker://` reference is unaffected by the
+ exemption.
+
## 0.5.0 - 2026-10-06
### Added
@@ -734,49 +779,6 @@ All notable changes to SkillEvaluator are documented in this file.
observations explicit, and reports unsupported or malformed JavaScript as
untrusted instead of a clean security result.
-### Security
-
-- The docs-publishing workflow, the only one that passes a secret to a step,
- now pins `actions/checkout` to a commit SHA, declares
- `permissions: contents: read`, and sets `persist-credentials: false`.
- `dco.yml` no longer persists checkout credentials either.
-- Docs are now published with the same Fern CLI version they are validated
- with. Both workflows install the CLI from `fern/package.json` and its
- committed lockfile; a test checks that the pin matches `fern/fern.config.json`.
-- Workflow hardening guards now glob `.github/workflows/` instead of a
- hardcoded two-file list, so every workflow — including any added later — must
- pin each action to a commit, avoid persisting checkout credentials, and
- declare a `permissions:` block. The guards also cover job-level
- `permissions:` overrides and job-level reusable-workflow `uses:` references,
- neither of which the step-level checks reached.
-- The Fern CLI is now installed from a committed lockfile, `fern/package-lock.json`,
- with `npm ci --prefix fern --ignore-scripts --omit=optional`, and both workflows
- invoke `./fern/node_modules/.bin/fern` rather than a binary on `PATH`. Previously
- `publish-docs.yml` ran `npm install`, which re-resolves every transitive
- dependency from semver ranges on each run: pinning `fern-api`'s own version
- pinned nothing beneath it. `@scarf/scarf` — reached through `fern-api`'s
- optional dependency on `@boundaryml/baml` — declares a `postinstall` script.
- The install step did not receive `FERN_TOKEN`, but its resulting CLI was later
- run in the token-bearing publish step. The lockfile pins every package to an
- exact version and integrity hash, `--ignore-scripts` stops lifecycle code
- running, and `--omit=optional` (which npm honours for this local install, but
- silently ignores for a `--global` one) leaves `fern-api` alone in the tree.
- Guards now permit only the reviewed lockfile install command in workflows,
- check the Fern manifest and lockfile dependency inputs, and require
- `fern/package.json`, `fern/package-lock.json`, and `fern/fern.config.json` to
- name the same CLI version. Fern dependency and config changes run the full
- CI lane, including dependency review, while `fern check` runs in both lanes.
- The developer-facing install instructions
- (`docs/README.md`, `docs/AGENTS.md`, `docs/developer-guide.mdx`) use the same
- lockfile install, so a contributor or agent following them gets the tree CI runs.
-- The action-pinning guard now accepts a same-repo composite action or
- reusable workflow (`uses: ./...`) without requiring a commit SHA, since
- GitHub always resolves a local reference from the caller's own commit and
- nothing about it can float. A local reference that escapes the repository
- (e.g. `./../outside`) or carries an `@ref` (a syntax local references don't
- have) is still rejected, and a `docker://` reference is unaffected by the
- exemption.
-
## 0.2.1 - 2026-08-24
### Added
diff --git a/CITATION.cff b/CITATION.cff
index 8d42f944..bf2186e3 100644
--- a/CITATION.cff
+++ b/CITATION.cff
@@ -2,7 +2,7 @@ cff-version: 1.2.0
message: "If you use SkillEvaluator in academic or technical work, please cite the methodology paper under preferred-citation and record the SkillEvaluator version used for reproducibility."
title: "SkillEvaluator"
type: software
-version: "0.5.0"
+version: "0.6.0"
authors:
- name: "NVIDIA Corporation"
license: Apache-2.0
diff --git a/docs/developer-guide.mdx b/docs/developer-guide.mdx
index b276d05a..aa85116c 100644
--- a/docs/developer-guide.mdx
+++ b/docs/developer-guide.mdx
@@ -146,7 +146,7 @@ SkillEvaluator version you used for reproducibility:
cff-version: 1.2.0
title: "SkillEvaluator"
type: software
-version: "0.5.0"
+version: "0.6.0"
preferred-citation:
type: article
title: "Evaluating Skills, Not Just Agents: Agentic Continuous Evaluation of Skills"
diff --git a/pyproject.toml b/pyproject.toml
index 4bb9b0dd..7941ae27 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -7,7 +7,7 @@ requires = ["setuptools >= 77", "wheel"]
[project]
name = "skillevaluator"
-version = "0.5.0"
+version = "0.6.0"
description = "Multi-tier framework for evaluating AI agent skills with quality gates, semantic overlap detection, synthetic evaluation dataset generation, and live agent evaluation."
authors = [{ name = "NVIDIA Corporation" }]
readme = "README.md"
diff --git a/src/skillevaluator/__init__.py b/src/skillevaluator/__init__.py
index d54a1889..89fee3bb 100644
--- a/src/skillevaluator/__init__.py
+++ b/src/skillevaluator/__init__.py
@@ -10,6 +10,6 @@ from importlib.metadata import PackageNotFoundError, version
try:
__version__ = version("skillevaluator")
except PackageNotFoundError:
- __version__ = "0.5.0"
+ __version__ = "0.6.0"
__all__ = ["__version__"]
diff --git a/uv.lock b/uv.lock
index 9b57dfe0..932c9890 100644
--- a/uv.lock
+++ b/uv.lock
@@ -2087,7 +2087,7 @@ wheels = [
[[package]]
name = "skillevaluator"
-version = "0.5.0"
+version = "0.6.0"
source = { editable = "." }
dependencies = [
{ name = "click" },