Repository navigation
chore: release main - #131
github-actions[bot] wants to merge 1 commit into
Conversation
9c1b6c8 to
82c576c
Compare
jeffdupont
left a comment
There was a problem hiding this comment.
Holding this release:
- Main CI is red at the commit this would ship. Run 38321949426 on
4d97cfa4failsskills.test.ts:418(root exports snapshot) andai-server api:check, both from #101 addingmakeGraphTrackData. #137 fixes it and is approved and green. Merge #137, then let release-please regenerate this PR. - Vercel packages can't publish. In the last release run (37987586310),
release-vercel-messagesandrelease-vercel-agentsfailed withnpm error 403 ... OIDC permission denied. npm still shows only0.0.0for both, so 0.2.0 never shipped and 0.2.1 will likely hit the same 403. npm trusted publishing needs setting up for both packages first.
The version bumps themselves look right: all patch releases, nothing to 1.0, ai-otel unchanged.
82c576c to
03512c4
Compare
jeffdupont
left a comment
There was a problem hiding this comment.
Re-checked at the regenerated head. One blocker cleared, one left.
Cleared: main CI is green now that #137 is merged (CI run on c4691cdc). The bumps are still all patches, nothing to 1.0, and ai-otel is unchanged.
Still blocking: @launchdarkly/ai-vercel-messages and @launchdarkly/ai-vercel-agents have never published. npm shows only 0.0.0 / 0.0.0-stage for both. The last release run that tried to publish them (37987586310, 9 Oct) failed with npm error 403 ... OIDC permission denied. The runs since succeeded only on days with nothing to publish. Unless npm trusted publishing has been configured for both packages, 0.2.1 will hit the same 403 and the release will go out without the two Vercel packages. Can someone with npm org access confirm the trusted-publisher setup for both packages before merging?
e6952e7 to
451de04
Compare
762f085 to
3c3d76c
Compare
3c3d76c to
4fbf2d2
Compare
…ic API (#154) Step 5 of AIC-3500 for JS, part 2: CI fails on a breaking change to the public API unless the PR declares it (checks 2 and 3, TESTING.md §5.2). The Python version is python-ai-sdk#196. Stacked on #153. **What changes** - `scripts/api-breaking.mjs` (plain Node, no dependencies, like `api-surface.mjs`) compares each non-experimental report declaration by declaration. - A removed or changed declaration is breaking, and so is a report present at base but gone at head. An added declaration is not. Comment-only changes such as doc comments or `@deprecated` don't count. - TypeScript's tool can't tell a compatible change from a breaking one (A.16), so an added optional member is flagged and passes with the `api-compatible` label. - `pr` mode passes when the title has `!` (same regex as Python) or the PR has `api-compatible`. - `release` mode runs on the release-please PR. For each package whose version changes, it compares against the package's last release tag (`<component>-<version>`, from `release-please-config.json`). A breaking change needs a major bump, or a minor one before 1.0. - `.github/workflows/api-compatibility.yml`: same triggers as Python's (`edited`, `labeled` and `unlabeled` re-run it) and the same release-PR detection (`release-please--branches--main`). The title goes through `env`, not shell interpolation. - 24 `node:test` tests (`yarn test:api-breaking`, run in CI) in a throwaway git repo. **Verified** - All repo checks pass, plus `yarn test:api-breaking` (24 passed). - A real `pr` run against part 1 and against `main` says "No breaking changes to the public API." - Changing `input?:` to `input:` in the openai-messages report fails and shows the old and new lines; with a `feat!:` title it passes. - `release` mode, with the manifest edited temporarily: client 0.4.0 → 0.4.1 fails (and passes with `api-compatible`), and 0.4.0 → 0.5.0 passes. - Five `ai-server` declarations have changed since `@launchdarkly/ai-server-0.4.0`. The open release PR #131 bumps the client to 0.5.0, which passes. I didn't run the script against that branch. **Known limit:** the provider packages have no report at their last release tag, so check 3 skips them, with a message, until their next release. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Overview** > Adds **API compatibility enforcement** so CI blocks undeclared breaking changes to committed API Extractor reports (`packages/*/etc/*.api.md`). > > A new `scripts/api-breaking.mjs` compares stable (non-experimental) reports declaration-by-declaration: removals, signature/type changes, and deleted reports count as breaking; additions do not; comment-only edits are ignored. **PR mode** fails unless the title uses conventional `!` (`feat!:`, etc.) or the PR has the `api-compatible` label. **Release mode** (release-please branch) compares each bumped package to its last release tag and requires a major bump (or pre-1.0 minor) when breaking diffs exist, with the same label escape hatch. > > A dedicated `.github/workflows/api-compatibility.yml` runs those checks on PR events (including title/label edits). Main `ci.yml` runs `yarn test:api-breaking` (24 fixture git tests). `AGENTS.md` documents the policy for contributors. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 08fbcc1. 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>
d6ec0d8 to
7673ab2
Compare
d8479e7 to
ab9cd9a
Compare
ab9cd9a to
273e545
Compare
🤖 I have created a release beep boop
@launchdarkly/ai-claude-agents: 0.5.0
0.5.0 (2026-10-23)
⚠ BREAKING CHANGES
Features
Bug Fixes
Dependencies
@launchdarkly/ai-claude-messages: 0.5.0
0.5.0 (2026-10-23)
⚠ BREAKING CHANGES
Features
Bug Fixes
Dependencies
@launchdarkly/ai-langchain-agents: 0.5.0
0.5.0 (2026-10-23)
⚠ BREAKING CHANGES
Features
Bug Fixes
Dependencies
@launchdarkly/ai-langchain-messages: 0.5.0
0.5.0 (2026-10-23)
⚠ BREAKING CHANGES
Features
Bug Fixes
Dependencies
@launchdarkly/ai-litellm-agents: 0.2.0
0.2.0 (2026-10-23)
⚠ BREAKING CHANGES
Features
Bug Fixes
Dependencies
@launchdarkly/ai-litellm-messages: 0.2.0
0.2.0 (2026-10-23)
⚠ BREAKING CHANGES
Features
Bug Fixes
Dependencies
@launchdarkly/ai-node: 0.4.0
0.4.0 (2026-10-23)
⚠ BREAKING CHANGES
Bug Fixes
Dependencies
@launchdarkly/ai-openai-agents: 0.5.0
0.5.0 (2026-10-23)
⚠ BREAKING CHANGES
Features
Bug Fixes
Dependencies
@launchdarkly/ai-openai-messages: 0.5.0
0.5.0 (2026-10-23)
⚠ BREAKING CHANGES
Features
Bug Fixes
Dependencies
@launchdarkly/ai-otel: 0.3.0
0.3.0 (2026-10-23)
⚠ BREAKING CHANGES
Bug Fixes
@launchdarkly/ai-server: 0.5.0
0.5.0 (2026-10-23)
⚠ BREAKING CHANGES
Experimental
Features
Bug Fixes
@launchdarkly/ai-typesafe: 0.2.0
0.2.0 (2026-10-23)
⚠ BREAKING CHANGES
Features
Bug Fixes
Dependencies
@launchdarkly/ai-vercel-agents: 0.3.0
0.3.0 (2026-10-23)
⚠ BREAKING CHANGES
Features
Bug Fixes
Dependencies
@launchdarkly/ai-vercel-messages: 0.3.0
0.3.0 (2026-10-23)
⚠ BREAKING CHANGES
Features
Bug Fixes
Dependencies
This PR was generated with Release Please. See documentation.