Skip to content

Agentplugins 0.1.80

Choose a tag to compare

@github-actions github-actions released this 08 Oct 08:42
Immutable release. Only release title and notes can be modified.
820a094

Native downloads: retain the companion THIRD_PARTY_NOTICES.txt with the binary and include it when redistributing.

What's Changed

  • fix: support Cursor active package projection by @777genius in #408
  • docs(installer): record automation-first product principle by @777genius in #342
  • fix(installer): fail-closed FIFO and non-directory plugin roots on Linux by @777genius in #338
  • feat(opencode): add native V2 MCP config codec by @777genius in #377
  • ci: pilot Ubicloud runners with GitHub rollback by @777genius in #405
  • feat: install plugins for Grok Build and Kimi Code by @777genius in #343
  • chore(deps): bump proxy-addr from 2.0.7 to 2.0.8 in /cli/internal/authoring/scaffold/templates by @dependabot[bot] in #407
  • feat(opencode): add typed native dialect transitions by @777genius in #378
  • chore(deps): update scaffold MCP SDK to 1.32.1 by @dependabot[bot] in #410
  • fix(agentplugins): isolate OpenCode executable version probes by @777genius in #411
  • feat(opencode): install and retain V2 native configuration by @777genius in #409
  • feat(opencode): recover native dialect migrations atomically by @777genius in #387
  • fix(opencode): protect native transition journals on Windows by @777genius in #412

Full Changelog: agentplugins-v0.1.78...agentplugins-v0.1.80

Installation verification

  • Draft qualification passed all six native targets and verified all nine attested release assets. Promotion published the same immutable assets.
  • Public npm launcher proof and public native installers passed on macOS, Linux, and Windows, each on AMD64 and ARM64.
  • The landing page shell and npx commands installed 0.1.80 in fresh Linux sandboxes and passed Context7 add/update/repair/remove for Codex and Cursor. An isolated Homebrew installation passed binary and companion notice hash checks and the formula test after tap synchronization.
  • npm publication succeeded. Public integrity, signatures, provenance, and the Codex/Cursor/Kiro lifecycle passed before its final OpenCode check failed because the harness lacked a native executable fixture. The failed OpenCode add/repair/remove phase was replayed successfully against the same public 0.1.80 package in a fresh sandbox, using the native version-only fixture in #414. Publication was not repeated.

The native bootstrap installer does not download THIRD_PARTY_NOTICES.txt automatically; retain this same-release companion with the binary. These checks qualify installer and launcher behavior with isolated client fixtures, not real native-client model/tool execution or standard authoring release qualification.