Repository navigation
chore: release main - #85
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
8 times, most recently
from
October 1, 2026 17:49
50267bf to
c47dc49
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
October 7, 2026 16:29
add00ca to
825f188
Compare
This was referenced Oct 7, 2026
XieX
added a commit
that referenced
this pull request
Oct 8, 2026
… needs (#119) ## Summary Pins `@launchdarkly/ai-server` to a specific version rather than `"*"`, and uses the `node-workspace` plugin for `release-please` to automatically update it as part of the release workflow. ## Details Every package that depends on `@launchdarkly/ai-server` asks for `"*"`. A consumer whose lockfile already holds an older ai-server keeps it when they upgrade a handler or `@launchdarkly/ai-node`, because `"*"` is still satisfied. That is already a problem on main: - Every handler imports `normalizeModelParameters` / `pickForwardedModelParameters`, which published `@launchdarkly/ai-server@0.3.0` does not export. As it stands, the next release (#85) would publish handlers that fail at import against a locked 0.3.0. - #71's `@launchdarkly/ai-node/experimental` re-exports `@launchdarkly/ai-server/experimental`. A pre-release review installed the packed ai-node with the published ai-server 0.3.0 and got `ERR_PACKAGE_PATH_NOT_EXPORTED`. ### Change - `release-please-config.json`: add the `node-workspace` plugin, so each release PR rewrites dependents' ranges to the version it releases. - All nine dependents: `"*"` → `"^0.3.0"`. The plugin keeps a `^`/`~`/`>=` prefix, but it turns `"*"` into an exact pin (`0.4.0`) and keeps it exact from then on. ### Why not just pin `^0.4.0` now Yarn v1 links a workspace sibling only when its version satisfies the range. Local `packages/client` stays at 0.3.0 until the release PR bumps it, so `^0.4.0` makes yarn go to npm, where 0.4.0 doesn't exist, and `yarn install --frozen-lockfile` fails with `Couldn't find any versions for "@launchdarkly/ai-server" that matches "^0.4.0"`. `^0.3.0` links the local package now, and `^0.4.0` links it once the release PR has bumped it. `yarn.lock` is unchanged either way, since yarn v1 doesn't lock workspace packages. ### Policy change to be aware of `node-workspace` gives every dependent a patch release, with a "Dependencies" changelog entry, whenever ai-server releases. It does this even when the dependent has no changes of its own, and release-please 17.6.0 has no option to turn it off (`always-link-local` is parsed but never read: googleapis/release-please#2876). The nine dependents are already in the pending release, so this release is unaffected. ### Verification - `yarn install --frozen-lockfile`, `yarn lint:pkg` (sherif), and the biome pre-commit hooks pass. - I ran `release-please release-pr --dry-run` (17.6.0, the version release-please-action v5.0.0 bundles) against this branch. It proposes the same versions as #85: ai-server 0.4.0, ai-node 0.3.0, ai-otel 0.2.0, handlers 0.4.0, vercel-* 0.2.0. Each of the nine dependents gets `@launchdarkly/ai-server bumped from ^0.3.0 to ^0.4.0` in its `package.json` and changelog. Merge this before #85. It doesn't conflict with #71, which doesn't touch these dependency lines or the release config. The Python SDK has the same unpinned `launchdarkly-ai-server` dependencies, but doesn't need a similar change yet. 🤖 Generated with [Claude Code](https://claude.com/claude-code), updated by @XieX <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Overview** > Replaces wildcard `@launchdarkly/ai-server` dependencies (`"*"`) with **`^0.3.0`** across nine workspace packages (`ai-node`, claude/openai/langchain/vercel agents and messages). That forces installs/upgrades to pull a compatible **ai-server** instead of keeping an older lockfile version that still satisfies `*`, which was breaking imports and experimental re-exports against published **0.3.0**. > > Adds the **`node-workspace`** plugin to **`release-please-config.json`** so future release PRs automatically bump dependents’ **ai-server** ranges when **packages/client** releases (e.g. `^0.3.0` → `^0.4.0` on the next cut). > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 1f3b9d3. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
October 8, 2026 19:29
d0cf05e to
1aaed9b
Compare
andrewklatzke
pushed a commit
that referenced
this pull request
Oct 8, 2026
…ing (#123) ## Summary Lists Agent Skills changes under an **Experimental** heading in each package's changelog, as TESTING.md §0.1 promises for an experimental feature. Spec: launchdarkly/ai-sdks-monorepo#50. Python twin: launchdarkly/python-ai-sdk#150. ## How `release-please-config.json` gains `changelog-sections`. Rows matching `feat`, `fix` and `perf` with scope `skills` map to "Experimental". The rest of the list reproduces the defaults release-please 17.6.0 uses for the Node strategy (the `conventionalcommits` preset's list), so every other commit renders exactly as before. Matching on scope works because release-please hands `changelog-sections` to `conventional-changelog-conventionalcommits` 6.1.0 unchanged (`manifest.ts:1397`), and the preset's `findTypeEntry` checks an entry's `scope` (`writer-opts.js:60-71`). The first match wins, so the scoped rows come first, and "Experimental" is therefore the first heading. `scope` isn't in release-please's documented config schema. Rerun the checks below when upgrading release-please. `AGENTS.md` gains a "PR Titles and the Changelog" section with the convention: - an experimental change uses its feature's scope, and only that one scope; - a PR that mixes core and experimental changes is split, or uses `BEGIN_COMMIT_OVERRIDE`; - a breaking experimental change uses `!` while the package is 0.x, and drops it after 1.0. The block sits at the end of the file so it doesn't conflict with #119, which adds `plugins` after `bootstrap-sha` (`git merge-tree` is clean). ## Verification - **Rendering:** I ran release-please 17.6.0's own commit parser and `DefaultChangelogNotes` against this config, with synthetic commits. - Non-experimental commits render byte-for-byte the same as with the defaults. - `feat(skills)`, `fix(skills)`, `perf(skills)` and `feat(skills)!` land under Experimental. A breaking one also appears in "⚠ BREAKING CHANGES". - `docs(skills)` stays hidden, `feat(skills,client)` lands under Features, and `feat(client)` stays under Features. - **Dry run:** `release-please release-pr --dry-run` against this branch proposes the same packages, versions and notes as release PR #85, apart from the date. Nothing on `main` uses the `skills` scope yet. - **Agent Skills:** #71 is retitled `feat(skills): Agent Skills`, so its squash commit lands under Experimental. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Overview** > Configures **release-please** so Agent Skills work (`feat`/`fix`/`perf` with scope `skills`) appears under an **Experimental** changelog heading, while the rest of the section list mirrors the default Node/conventional-commits preset so other commits render unchanged. > > Adds **PR Titles and the Changelog** to `AGENTS.md`, documenting squash-merge titles, the single `skills` scope, mixed core/experimental PRs (`BEGIN_COMMIT_OVERRIDE`), breaking experimental commits while packages are 0.x, and removing experimental rows when a feature graduates. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 5c1e697. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
3 times, most recently
from
October 9, 2026 17:19
555319b to
87d81de
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
October 9, 2026 19:43
87d81de to
4acc72c
Compare
2 tasks
andrewklatzke
added a commit
that referenced
this pull request
Oct 9, 2026
… release (#130) ## Summary - `@launchdarkly/ai-vercel-agents` and `@launchdarkly/ai-vercel-messages` are already in `release-please-config.json`, so the open release (#85) will tag them and open GitHub releases. - The publish workflow never listed those packages, so the npm tarballs would not be published. This adds the same release and manual-publish jobs the other handler packages use. ## Test plan - [ ] Confirm the workflow lists `packages/vercel-agents` and `packages/vercel-messages` in the dispatch choices, release outputs, and publish jobs. - [ ] Merge this before #85. If that release merges first, re-run a manual publish for both packages; release-please will not cut 0.2.0 again. Made with [Cursor](https://cursor.com)
andrewklatzke
self-requested a review
October 9, 2026 20:26
andrewklatzke
approved these changes
Oct 9, 2026
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
@launchdarkly/ai-claude-agents: 0.4.0
0.4.0 (2026-10-09)
Features
Bug Fixes
Dependencies
@launchdarkly/ai-claude-messages: 0.4.0
0.4.0 (2026-10-09)
Features
Bug Fixes
Dependencies
@launchdarkly/ai-langchain-agents: 0.4.0
0.4.0 (2026-10-09)
Features
Bug Fixes
Dependencies
@launchdarkly/ai-langchain-messages: 0.4.0
0.4.0 (2026-10-09)
Features
Bug Fixes
Dependencies
@launchdarkly/ai-node: 0.3.0
0.3.0 (2026-10-09)
Experimental
@launchdarkly/ai-server/experimental, re-exported from@launchdarkly/ai-node/experimental(a242659)Features
initClient(client, options)accepts telemetry options for a pre-initialized client (a242659)initClientoptions instead of ignoring them silently (a242659)Bug Fixes
shutdownTelemetry()releases the OpenTelemetry globals the SDK registered, so a laterinitClientexports spans again (a242659)initClient(client)returns the client already set instead of replacing it (a242659)initClientthat fails, or thatshutdown()interrupts, closes the client it built, and a failure is no longer cached, so the next call retries (a242659)Dependencies
@launchdarkly/ai-openai-agents: 0.4.0
0.4.0 (2026-10-09)
Features
Bug Fixes
Dependencies
@launchdarkly/ai-openai-messages: 0.4.0
0.4.0 (2026-10-09)
Features
Bug Fixes
Dependencies
@launchdarkly/ai-otel: 0.2.0
0.2.0 (2026-10-09)
Features
@launchdarkly/ai-server: 0.4.0
0.4.0 (2026-10-09)
Experimental
@launchdarkly/ai-server/experimental, re-exported from@launchdarkly/ai-node/experimental(a242659)Features
initClient(client, options)accepts telemetry options for a pre-initialized client (a242659)initClientoptions instead of ignoring them silently (a242659)Bug Fixes
shutdownTelemetry()releases the OpenTelemetry globals the SDK registered, so a laterinitClientexports spans again (a242659)initClient(client)returns the client already set instead of replacing it (a242659)initClientthat fails, or thatshutdown()interrupts, closes the client it built, and a failure is no longer cached, so the next call retries (a242659)@launchdarkly/ai-vercel-agents: 0.2.0
0.2.0 (2026-10-09)
Features
Bug Fixes
Dependencies
@launchdarkly/ai-vercel-messages: 0.2.0
0.2.0 (2026-10-09)
Features
Bug Fixes
Dependencies
This PR was generated with Release Please. See documentation.
Note
Overview
Release Please monorepo cut that bumps published versions in
.release-please-manifest.json, each package’spackage.json/src/version.ts, and adds matching CHANGELOG sections (including first changelogs for the Vercel packages). Provider packages now depend on@launchdarkly/ai-server^0.4.0.The documented release for
@launchdarkly/ai-server0.4.0 (and aligned provider bumps) includes dual ESM + CommonJS builds, agent graph node streaming, per-node tracking events and public-helper usage telemetry,initClient/shutdownTelemetrylifecycle fixes, and experimental Agent Skills under@launchdarkly/ai-server/experimental. Cross-cutting fixes in the notes cover AI Configmodel.parametersforwarding (allowlists, snake_case → camelCase), message-handler tool authorization (SEC-9507), and Vercel adapter parameter mapping and multimodal content handling.Reviewed by Cursor Bugbot for commit 4acc72c. Bugbot is set up for automated code reviews on this repo. Configure here.