[jeffdupont]

Steps 1 and 3 of AIC-3673. The Python half is launchdarkly/python-ai-sdk#242.

What this does

• release-as: 1.0.0 on all 14 packages in release-please-config.json. The node-workspace plugin updates the internal dependency ranges.
• Publish jobs for litellm-agents and litellm-messages. They had none, so @launchdarkly/ai-litellm-*-0.2.0 was tagged but never published. Both are also added to the manual-publish choices.

changelog-sections is left alone: #181 (merged) removed the evaluations Experimental rows when it promoted Evaluations from Code to core.

⚠️ npm setup: trusted publishers still to confirm for 5 of 14 packages

The 26 Oct release run (40393827352) failed 3 publish jobs, and the litellm packages have never had a job:

Package	On npm	Failure
@launchdarkly/ai-typesafe	0.0.0 placeholder	E404 … PUT @launchdarkly/ai-typesafe: the package doesn't exist, and OIDC can't create it
@launchdarkly/ai-vercel-agents	0.0.0 placeholder	E403 OIDC permission denied
@launchdarkly/ai-vercel-messages	0.0.0 placeholder	E403 OIDC permission denied
@launchdarkly/ai-litellm-agents	0.0.0 placeholder	no publish job (added here)
@launchdarkly/ai-litellm-messages	0.0.0 placeholder	no publish job (added here)

Before the release PR merges, an npm org admin needs to:

1. Publish a 0.0.0 placeholder for ai-typesafe, ai-litellm-agents and ai-litellm-messages. Done: all three are on npm at 0.0.0 (checked 29 Oct).
2. Add a trusted publisher (launchdarkly/js-ai-sdk, workflow release-please.yml) to all five.

Otherwise 1.0.0 ships 9 of 14 packages.

Merge this last

Merge this only after the items below are done. Anything merged before the release PR (#171) merges ships in 1.0.0, and a ! change merged after 1.0 forces 2.0.

• feat(evaluations)!: promote Evaluations from Code to core #181 feat(evaluations)!: promote Evaluations from Code to core. After it, @launchdarkly/ai-server/experimental exports nothing.
• fix(SEC-9507)!: dispatch tools only from the active variation's config.tools #180 fix(SEC-9507)!: dispatch tools only from the active variation's config.tools
• fix(claude-agents)!: honour the config's max_tokens and disable thinking unless the config asks #183 fix(claude-agents)!: honour max_tokens and disable thinking by default
• feat(AIC-3439)!: let wildcard handlers accept only named providers #111 feat(AIC-3439)!: wildcard handlers accept only named providers (merged 29 Oct)
• npm placeholders (above)
• Trusted publishers on all five packages (confirmed 30 Oct: all five use release-please.yml) (above; needs an npm org admin to confirm)
• fix(AIC-3592): make native LangGraph hand-offs complete #192 fix(AIC-3592): make native LangGraph hand-offs complete (ready for review; spec launchdarkly/ai-sdks-monorepo#118)
• fix(AIC-3573): never send a NativeTool to the model as a function tool #194 fix(AIC-3573): never send a NativeTool to the model as a function tool (ready for review; spec launchdarkly/ai-sdks-monorepo#116)
• feat(client)!: capture conversation content by default and add configure() #190 feat(client)!: capture conversation content by default and add configure() (approved; breaking, so it must land before chore: release main #171)
• test(AIC-3716): run the OpenAI native graph with a tool on the real SDK #196 test(AIC-3716): run the OpenAI native graph with a tool on the real SDK (test only; optional for the release)

After merging

1. Confirm the regenerated chore: release main #171 lists 1.0.0 for all 14 packages and its CI is green, then merge it.
2. Install each package from npm into an empty project and import its entry points, in both ESM and CJS (AIC-3673 step 5).
3. Open a PR removing release-as straight away.

Checks

• The workflow YAML parses: 14 per-package publish jobs plus release-please and the canary. The new jobs are copies of release-typesafe.
• No local build was run: this is config only, made through the GitHub API.

🤖 Generated with Claude Code

---

Note

Overview
Prepares the monorepo for a coordinated 1.0.0 npm release by setting release-as: "1.0.0" on all 14 workspaces in release-please-config.json (the node-workspace plugin will align internal dependency ranges when the release PR lands).

The release-please workflow now fully covers litellm-agents and litellm-messages: they appear in manual workflow_dispatch package choices, expose release-please job outputs, and get dedicated release-litellm-* publish jobs (build, attest, npm publish) matching the other packages—closing the gap where LiteLLM tags could be created without a publish step.

^{Reviewed by Cursor Bugbot for commit af882d4. Bugbot is set up for automated code reviews on this repo. Configure here.}