chore: release main#1025
Merged
Merged
Conversation
## Summary - Simplifies the breaking-change CI job to always use `git merge-base HEAD origin/main` as the base, regardless of event type or current branch. Previously, the job had three branches (PR base SHA / merge-base with main on `next` / merge-base with `next` otherwise), one of which was unreachable due to a `--abrev-ref` typo. - Renames the job to `detect_breaking_changes_vs_main` (display name `detect-breaking-changes-vs-main`, step name "Detect breaking changes vs. main") to leave room for a future check that runs against feature-branch history. - Drops the `next` fetch since it's no longer needed. - I'll follow up later with a separate "check for breaking changes long a branch's history" since that's a lower priority than this - ## Test plan - [ ] CI on this PR runs the new job and reports `detect-breaking-changes-vs-main` as a check. - [ ] The job correctly resolves a non-empty `BASE_SHA` against `origin/main` for this PR. - [ ] No other workflow or repo configuration depends on the old job name (branch protection is not enabled for this repo, per discussion).
…d auth profiles Add helpers for performing Workload Identity Federation based identity auth, as well as support for interactive OAuth and profile management.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
b347b8a to
7e96066
Compare
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| */ | ||
| private _applyCredentialBaseURL(baseURL: string | undefined): void { | ||
| if (!baseURL) return; | ||
| const normalized = baseURL.replace(/\/+$/, ''); |
| options: ResolverOptions, | ||
| ): CredentialResult { | ||
| const credentialsPath = config.authentication.credentials_path ?? null; | ||
| const effectiveBaseURL = (config.base_url || options.baseURL).replace(/\/+$/, ''); |
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
7e96066 to
7c289d2
Compare
packyg
approved these changes
May 4, 2026
Contributor
Author
stainless-app Bot
pushed a commit
that referenced
this pull request
May 28, 2026
) ## Why The beta streaming accumulator's `compaction_delta` handler copied only `content` onto the accumulated compaction block, silently dropping `encrypted_content` — opaque metadata the caller must round-trip verbatim to keep context across compaction boundaries. A streamed message therefore lost it relative to the non-streaming response. Same bug fixed in anthropic-python#1821 and ported to anthropic-go. ## The fix One line in `src/lib/BetaMessageStream.ts` — carry `encrypted_content: event.delta.encrypted_content` alongside `content` in the `compaction_delta` case. ## Testing Turns the shared `beta/compaction_encrypted_content` accumulator snapshot green (verified locally with both branches combined); existing MessageStream/BetaMessageStream suites still pass. Snapshot test lands in the companion test PR — merge this before/with it so `next` never goes red. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Merged
stainless-app Bot
pushed a commit
that referenced
this pull request
May 29, 2026
) ## Why The beta streaming accumulator's `compaction_delta` handler copied only `content` onto the accumulated compaction block, silently dropping `encrypted_content` — opaque metadata the caller must round-trip verbatim to keep context across compaction boundaries. A streamed message therefore lost it relative to the non-streaming response. Same bug fixed in anthropic-python#1821 and ported to anthropic-go. ## The fix One line in `src/lib/BetaMessageStream.ts` — carry `encrypted_content: event.delta.encrypted_content` alongside `content` in the `compaction_delta` case. ## Testing Turns the shared `beta/compaction_encrypted_content` accumulator snapshot green (verified locally with both branches combined); existing MessageStream/BetaMessageStream suites still pass. Snapshot test lands in the companion test PR — merge this before/with it so `next` never goes red. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
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
3 participants
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.
✨ Stainless prepared a new release
sdk: 0.93.0
0.93.0 (2026-05-04)
Full Changelog: sdk-v0.92.0...sdk-v0.93.0
Features
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions