Skip to content

core v2.1.1

Choose a tag to compare

@github-actions github-actions released this 13 Jul 15:08
e754bd4

Added

  • Repo-root monkeybot_config_example/ — full-option human-readable config templates (.example filenames).
  • monkeybot new also scaffolds permissions.yaml.
  • monkeybot new writes an agent-project pyproject.toml with a PyPI monkeybot[<provider>]>=2.1.0,<3 dependency (plain uv sync after scaffold).
  • monkeybot new interactive menus (and --with) select additional providers/features into that same monkeybot[…] dep list.
  • scripts/smoke_global_cli.sh — local-wheel stand-in for clean-machine PyPI smoke (uv tool installnewuv syncvalidate/doctor/chat).
  • README / getting-started / onboarding skill lead with uv tool install monkeybot-cli (clone is contributor-only).
  • monkeybot-cli declares published core bound monkeybot[cli]>=2.1.0,<3 (local clones still use [tool.uv.sources]).

Changed

  • monkeybot doctor remediation for missing extras: add monkeybot[<extra>] to agent deps + uv sync (keeps uv sync --extra only when the agent defines project-level optionals).

  • fake provider credentials treated as optional in doctor (smoke / no-API-key path).

  • publish-release.yml Trusted-Publishes to PyPI (OIDC) packages tagged in that run only — core before cli; scripts/release.py publish emits packages via GITHUB_OUTPUT.

  • Remove redundant CLI hatch force-include of scaffold_defaults (duplicated wheel paths and broke uv build).

  • Scaffold templates and run_new moved into monkeybot-cli (monkeybot_cli.scaffold / scaffold_defaults). Harness monkeybot.scaffold is a compatibility shim; Docker installs the CLI to scaffold at image build.

  • monkeybot-cli version bumped to 0.2.0.

  • README integrations tables aligned with v2.0.0 shipped scope (per CHANGELOG); removed speculative "Coming Soon" items to BACKLOG.md with a short near-term roadmap.

  • Reframed public positioning: multi-cloud-capable harness with GCP-first docs (README, cloud deployment design, getting started, features, Pattern A guide). Clarifies this is not a universal integration catalog; documents AWS shipped paths alongside GCP examples.