Skip to content

release: 6.2.1#2765

Open
stainless-app[bot] wants to merge 5 commits into
mainfrom
release-please--branches--main--changes--next--components--cloudflare
Open

release: 6.2.1#2765
stainless-app[bot] wants to merge 5 commits into
mainfrom
release-please--branches--main--changes--next--components--cloudflare

Conversation

@stainless-app
Copy link
Copy Markdown
Contributor

@stainless-app stainless-app Bot commented May 15, 2026

Automated Release PR

6.2.1 (2026-05-18)

Full Changelog: v6.2.0...v6.2.1


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

musa-cf added 2 commits May 15, 2026 10:42
Add continue-on-error: true to the test and detect-breaking-changes
jobs so they still run but do not fail CI. These jobs are informational
and should not gate release readiness.

Refs: APIX-852
ci: make test and detect-breaking-changes jobs non-blocking
musa-cf and others added 3 commits May 18, 2026 10:59
Job-level continue-on-error only prevents workflow failure but the job
itself still reports as failed, which blocks PRs when the job is a
required status check. Moving it to the step level makes the job
conclude as success while still surfacing failures in the step output.

Refs: APIX-852
ci: move continue-on-error from job level to step level
@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--cloudflare branch from c87dd3f to b17edc9 Compare May 18, 2026 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant