Repository navigation
chore: release main - #142
Merged
Merged
Conversation
andrewklatzke
self-requested a review
October 5, 2026 21:44
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
5 times, most recently
from
October 8, 2026 18:10
d04a021 to
5e57d7e
Compare
andrewklatzke
pushed a commit
that referenced
this pull request
Oct 8, 2026
…gelog heading (#150) ## Summary Lists changes to the two experimental features under an **Experimental** heading in each package's changelog, as TESTING.md §0.1 promises. The features are Agent Skills (scope `skills`) and Evaluations from Code (scope `evaluations`). Spec: launchdarkly/ai-sdks-monorepo#50. JS twin: launchdarkly/js-ai-sdk#123. ## How `release-please-config.json` gains `changelog-sections`. Rows matching `feat`, `fix` and `perf` with scope `skills` or `evaluations` map to "Experimental". The rest of the list reproduces release-please 17.6.0's Python-strategy defaults (`strategies/python.ts:31-44`), which keep `deps` and a visible "Documentation" section, 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. ## Effect on the pending release `release-please release-pr --dry-run` against this branch proposes the same five packages and versions as release PR #142. The one difference is the point of this PR: the `evaluations` commits move out of "Features" and "Bug Fixes" into "Experimental" for `launchdarkly-ai-server` 0.3.0 and `launchdarkly-ai-python` 0.2.0. They also still appear in "⚠ BREAKING CHANGES". `docs(evaluations)` stays under "Documentation". If this merges before #142, the 0.3.0 changelog will show that split. ## 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 Python defaults, and the scoped commits land under Experimental. - **Dry run:** compared with #142, as above. - **Agent Skills:** #87 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** > Adds **`changelog-sections`** to `release-please-config.json` so squash-merged `feat`/`fix`/`perf` commits with scope **`skills`** or **`evaluations`** appear under an **Experimental** heading in package changelogs; other commit types keep the usual Python release-please sections (Features, Bug Fixes, etc.), with scoped rules listed first so they win matching. > > Documents the same conventions in **`AGENTS.md`** under **PR Titles and the Changelog**: single-scope experimental PR titles, splitting or `BEGIN_COMMIT_OVERRIDE` when mixing core and experimental work, and how `!` applies to breaking experimental changes before/after 1.0. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 0df5fb1. 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 19:43
5264878 to
af94009
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
October 9, 2026 20:04
af94009 to
c2a6a78
Compare
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-server: 0.3.0
0.3.0 (2026-10-09)
⚠ BREAKING CHANGES
Experimental
launchdarkly_ai_server.experimental.skills(dfb519c)Features
init_clientoptions instead of ignoring them silently (dfb519c)Bug Fixes
init_clientadopts a client only after telemetry setup succeeds, and closes a client it built when setup fails (dfb519c)shutdown()releases the global OpenTelemetry tracer provider the SDK registered, so a laterinit_clientexports spans again (dfb519c)Documentation
launchdarkly-ai-python: 0.2.0
0.2.0 (2026-10-09)
⚠ BREAKING CHANGES
Experimental
launchdarkly_ai_server.experimental.skills(dfb519c)Features
init_clientoptions instead of ignoring them silently (dfb519c)Bug Fixes
init_clientadopts a client only after telemetry setup succeeds, and closes a client it built when setup fails (dfb519c)shutdown()releases the global OpenTelemetry tracer provider the SDK registered, so a laterinit_clientexports spans again (dfb519c)launchdarkly-ai-claude-agents: 0.2.5
0.2.5 (2026-10-09)
Features
launchdarkly-ai-claude-messages: 0.2.4
0.2.4 (2026-10-09)
Features
launchdarkly-ai-openai-agents: 0.2.5
0.2.5 (2026-10-09)
Features
Bug Fixes
launchdarkly-ai-openai-messages: 0.2.4
0.2.4 (2026-10-09)
Features
launchdarkly-ai-langchain-agents: 0.2.5
0.2.5 (2026-10-09)
Features
Bug Fixes
launchdarkly-ai-langchain-messages: 0.2.4
0.2.4 (2026-10-09)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.
Note
Overview
Release-only PR (Release Please): bumps package versions,
__version__strings,.release-please-manifest.json, andCHANGELOG.mdentries—no application source changes in the diff.launchdarkly-ai-server0.3.0 andlaunchdarkly-ai-python0.2.0 document breaking evaluation tool APIs:Tool→ frozenEvalTool, tools passed as a list (with inline definitions), andtools.getis async. Also ships experimental evaluations work (remote AI config model resolution,tools=override) andlaunchdarkly_ai_server.experimental.skills, plusinit_client/shutdowntelemetry lifecycle fixes and warnings for unrecognizedinit_clientoptions.Provider packages (0.2.4–0.2.5) mainly add SDK usage telemetry for which public helpers apps call (AIC-3495), with LangChain fixes (strip
toolsfrom model ctor kwargs; accept sync tool handlers on invoke/graphs) and the same sync-handler fix on OpenAI agents.Reviewed by Cursor Bugbot for commit c2a6a78. Bugbot is set up for automated code reviews on this repo. Configure here.