Files
davida-ps c1d1824f86 ci(skills): publish release trust packets + expand skill installer awareness (vercel) (#262)
* ci(skills): publish release trust packets

* ci(skills): simulate beta tag releases

* ci(skills): match release version bump rules

* chore(skills): group agent skills for installer

* chore(skills): make clawtributor global

* chore(skills): bump all skills for trust release

* ci(skills): require npx install docs

* fix(skills): simulate prerelease tag versions

* fix(skills): aggregate trust artifact checksum failures

* fix(frontend): advertise npx skills suite install

* chore(frontend): drop ad hoc homepage copy test

* fix(ci): run skill release tooling tests
2026-06-10 13:22:22 +03:00

5.8 KiB

Changelog

[0.1.7] - 2026-06-10

Changed

  • Re-released skill package with updated marketplace grouping and signed release trust artifacts for Vercel-compatible skill installation.

[0.1.6] - 2026-05-16

Fixed

  • Added scripts/load_suppression_config.mjs to skill.json SBOM metadata so release archives include the helper imported by scripts/render_report.mjs.

[0.1.5] - 2026-05-14

Security

  • Added explicit signed release artifact verification instructions for standalone installs, including checksums.json, checksums.sig, signing-public.pem, archive hash verification, and SKILL.md/skill.json checksum checks.

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[0.1.4] - 2026-04-17

Changed

  • Re-released metadata and docs updates under a new version after detecting that 0.1.3 was already present in ClawHub with older artifact content.
  • No runtime behavior changes to audit execution, cron setup, or report delivery logic.

[0.1.3] - 2026-04-16

Changed

  • scripts/setup_cron.mjs keeps the same cron setup behavior while removing direct spawnSync( call tokens that triggered static moderation false positives.
  • Test harness process launch calls now use local aliases, preserving test behavior while avoiding false-positive dangerous_exec signatures.
  • Frontmatter metadata now declares runtime requirements directly under metadata.openclaw.requires (bins + required env) so published manifest metadata aligns with the skill's documented/runtime behavior.
  • Added explicit metadata.openclaw.envVars declarations for DM/email delivery variables used by the scheduled workflow.
  • Removed curl from required runtime bins in the manifest metadata; it remains an installation-flow helper, not a runtime requirement.

Security

  • Added a skill-local .clawhubignore that excludes test/ from publish payloads.
  • This prevents moderation from scanning non-runtime test harness files that previously generated suspicious.dangerous_exec findings.

[0.1.2] - 2026-04-14

Added

  • Registry/runtime metadata now declares the actual required runtimes (openclaw, node) plus the DM/email environment variables and operator review notes.
  • scripts/setup_cron.mjs now prints a preflight review summarizing recipients, persistence, and required runtime before creating or updating the cron job.
  • Coverage for cron setup disclosure behavior (test/setup_cron.test.mjs) and case-insensitive suppression matching regression.

Changed

  • Email delivery is now explicit and opt-in: scripts/runner.sh only attempts email delivery when PROMPTSEC_EMAIL_TO is configured.
  • scripts/setup_cron.mjs now carries configured runtime/delivery environment variables into the cron payload so the scheduled job is more self-describing and less dependent on ambient host state.
  • Suppression matching in scripts/render_report.mjs is now case-insensitive for skill names, matching the documented behavior and normalized config loader.
  • Documentation now consistently refers to the current OpenClaw product name.

Security

  • Removed the placeholder email recipient from the default cron payload to avoid implicitly sending audit output to an unreviewed address.
  • Cron setup now surfaces the unattended delivery model before enabling persistence, making external recipients and runtime assumptions explicit to the operator.

[0.1.1]

Added

  • Contributor credit: portability and path-hardening improvements in this release were contributed by @aldodelgado in PR #62.
  • Cross-shell home-path expansion support in watchdog path inputs (~, $HOME, ${HOME}, %USERPROFILE%, $env:HOME).
  • Regression coverage for suppression-config home-token expansion and escaped-token rejection (test/suppression_config.test.mjs).

Changed

  • scripts/codex_review.sh now resolves the Codex CLI from CODEX_BIN, then PATH, then Homebrew fallback for improved portability.
  • scripts/setup_cron.mjs now normalizes and validates install-dir/home-derived paths before job creation.
  • scripts/load_suppression_config.mjs now resolves/normalizes configured file paths consistently across shell styles.

Security

  • Escaped or unresolved home tokens in suppression config paths now fail fast to avoid silently using unintended literal paths.

[0.1.0]

Added

  • Suppression/allowlist mechanism with explicit opt-in gating (defense in depth).
  • --enable-suppressions CLI flag for run_audit_and_format.sh, render_report.mjs, and runner.sh.
  • enabledFor config sentinel -- config must declare "enabledFor": ["audit"] for audit suppression to activate.
  • 4-tier config file resolution: explicit --config path > OPENCLAW_AUDIT_CONFIG env var > ~/.openclaw/security-audit.json > .clawsec/allowlist.json.
  • INFO-SUPPRESSED section in report output showing suppressed findings with metadata.
  • Integration tests for suppression behavior (11 tests in render_report_suppression.test.mjs).
  • Unit tests for config loading and opt-in gating (15 tests in suppression_config.test.mjs).
  • Test fixtures: empty-suppressions.json, invalid-json.json, malformed-config.json.

Changed

  • load_suppression_config.mjs now requires explicit { enabled: true } parameter -- returns empty suppressions by default.
  • render_report.mjs passes suppression enabled state to config loader.
  • Summary counts in report output are recalculated after filtering suppressed findings.

Security

  • Suppression is never active by default -- requires BOTH CLI flag AND config sentinel (defense in depth).
  • Environment variables alone cannot activate suppression (prevents ambient attack vector).