Skip to content

chore(master): release 0.10.0#130

Merged
jithin23-kv merged 3 commits into
masterfrom
release-please--branches--master--components--agent-opfor
Jul 6, 2026
Merged

chore(master): release 0.10.0#130
jithin23-kv merged 3 commits into
masterfrom
release-please--branches--master--components--agent-opfor

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.10.0 (2026-07-06)

⚠ BREAKING CHANGES

  • sdk: switch to apikey values; update sdk e2e tests and examples (#168)

Features

  • expand env references in agent target headers (#169) (605a9b5)
  • stream run lifecycle events as ndjson via a run-listener (#159) (ccc99dc)
  • support listing mcp suites from the sdk (#144) (6b68b42)
  • support server-owned session IDs with body/header config (#167) (121edfd)

Bug Fixes

  • broken gitleaks ci for fork (#158) (e0be561)
  • bump zod to ^4.0.0 to satisfy claude-agent-sdk peer dependency (#148) (bcd970e)
  • conditional reasoning instruction and stricter section() parsing (15b598f)
  • declare mcp dep, add createRequire banner, fix atlas-data resolution for bundled runners (#134) (b8ff91f)
  • harden mcp baseline scanner against false negatives and crashes (#155) (cd36f85)
  • make agent judge reason before stating its verdict (3b551c6)
  • make agent judge reason before stating its verdict (60dacc8)
  • make hunt work from a published install (#157) (ac468ea)
  • rename 'Risk Score' to 'Safety Score' in extension popup (#133) (4c955a0)
  • revert gitleaks trigger from pull_request_target to pull_request (#161) (ea7315e)
  • run gitleaks binary in ci to unblock fork pull requests (#162) (be307b2)
  • use simple tag format for release-please (9e7a8e6)
  • validate mcp tool inputs with zod and return actionable errors (#143) (ad749bc)

Refactors

  • sdk: switch to apikey values; update sdk e2e tests and examples (#168) (ed40cea)

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot changed the title chore(master): release agent-opfor 0.9.1 chore(master): release 0.9.1 Jun 26, 2026
@github-actions github-actions Bot force-pushed the release-please--branches--master--components--agent-opfor branch 12 times, most recently from e419787 to 8fa8b07 Compare July 3, 2026 09:41
@github-actions github-actions Bot force-pushed the release-please--branches--master--components--agent-opfor branch 7 times, most recently from 96be2d7 to 2fb1c84 Compare July 6, 2026 10:44
@github-actions github-actions Bot changed the title chore(master): release 0.9.1 chore(master): release 0.10.0 Jul 6, 2026
@github-actions github-actions Bot force-pushed the release-please--branches--master--components--agent-opfor branch from 2fb1c84 to ba8daa9 Compare July 6, 2026 12:21
@github-actions github-actions Bot force-pushed the release-please--branches--master--components--agent-opfor branch from ba8daa9 to c87e53a Compare July 6, 2026 12:31
core@0.10.0 no longer satisfies the ^0.9.0 range in cli/mcp/sdk
(0.x caret ranges don't cross minor versions), so npm fell back to
the registry for the unpublished core package and 404'd. Bump the
ranges to ^0.10.0 and regenerate the lockfiles to match.
…e bump

runners/sdk was bumped to 0.10.0 but tests/e2e/sdk still pinned
^0.9.0 (not in release-please's extra-files list), so npm installed
the published 0.9.0 sdk from the registry instead of linking the
local workspace. That published version predates the apiKey-literal
support added in PR #168, so the e2e tests failed with a missing
LLM_API_KEY env var. Bump the range and regenerate the lockfile.
@jithin23-kv jithin23-kv merged commit c4eb9cc into master Jul 6, 2026
7 checks passed
@jithin23-kv jithin23-kv deleted the release-please--branches--master--components--agent-opfor branch July 6, 2026 13:05
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant