Skip to content

release: 0.51.0#74

Merged
github-actions[bot] merged 2 commits into
mainfrom
release-please--branches--main--changes--next
May 19, 2026
Merged

release: 0.51.0#74
github-actions[bot] merged 2 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app

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

Copy link
Copy Markdown
Contributor

Automated Release PR

0.51.0 (2026-05-19)

Full Changelog: v0.50.0...v0.51.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

@thurgood-bot

thurgood-bot Bot commented May 19, 2026

Copy link
Copy Markdown

Oppenheimer Cleanup Review

Repo-wide search shows no remaining references to the removed Worker APIs or autoShutdownMinutes fields in the current codebase, so there is no internal dead code to simplify beyond what this release PR already removed. No additional safe deletions or collapses are provable from the diff alone without external consumer analysis.

⚠️ Risk If Removed (2)

Removing these items could have subtle side effects. Review the documented risks before proceeding.

  • src/ServiceContracts/Agent/SkillsContract.php:1: Empty marker interface remains with no repo references; 0 references found via repo-wide grep for "SkillsContract" (only the definition file is present). This is likely scaffolding and not used internally, but external consumers could type-hint it.

    If this is purely scaffolding and not part of the public API surface, delete the empty interface; otherwise keep and document intended usage.

  • src/ServiceContracts/Agent/SkillsRawContract.php:1: Empty marker interface remains with no repo references; 0 references found via repo-wide grep for "SkillsRawContract" (only the definition file is present). Internal usage is absent, but external consumers could type-hint it.

    If not part of the public surface, delete the empty interface; otherwise keep and document intended usage.

✅ Keep (Justified) (2)

These items are actually needed. Explanations below.

  • src/Services/WorkerService.php:1: Worker service was removed in this PR and there are 0 references to "WorkerService", "WorkerRawService", "worker->", or "V1Proxy" across the repo per repo-wide grep. This suggests internal code is already fully removed; no further action needed.

    Keep as-is; the removal already matches the evidence. No additional internal cleanup remains.

  • src/Compute/V1/Instances/InstanceCreateParams.php:1: autoShutdownMinutes field and accessors were removed; repo-wide grep for "autoShutdownMinutes" returns 0 references. This indicates no internal usage remains.

    Keep as-is; removal appears complete and safe within the repo.


Cleanup review by Oppenheimer | Re-run with /cleanup

@thurgood-bot

thurgood-bot Bot commented May 19, 2026

Copy link
Copy Markdown

Judicial Review

Release 0.51.0 adds the new agent skills namespaces surface and removes worker-related APIs and compute auto-shutdown parameters. No critical legal-grade risks found, but there are breaking SDK contract changes to call out.

Findings: 0 critical, 2 warnings, 0 info

API Contracts

⚠️ WARNING in src/Client.php:48

Removal of the public worker service from the client is a breaking SDK contract change for consumers relying on Client::$worker and Worker services.

Recommendation: Add a deprecation shim (e.g., keep worker with a deprecation notice) or clearly document the removal and provide migration guidance in the changelog/release notes; consider a major version bump if semver applies.

⚠️ WARNING in src/Compute/V1/Instances/InstanceCreateParams.php:19

The autoShutdownMinutes parameter and corresponding response fields were removed from the compute instance APIs, which is a breaking change for clients expecting to set or read this value.

Recommendation: Either keep the field as deprecated (ignore on server) for backward compatibility or explicitly document the removal and migration path; if the API truly removed it, bump the major version or add a compatibility layer.


Legal-Grade review by Thurgood | Re-review with /review

@thurgood-bot

thurgood-bot Bot commented May 19, 2026

Copy link
Copy Markdown

DB Cooper Database Review

Reviewed the release PR diff with DB risk focus; changes are SDK/service surface updates with no database schema, migration, or query changes evident in the diff provided.

No database risks found. Migrations and DB-impacting changes look safe.


DB review by DB Cooper | Re-run with /dbreview

@github-actions github-actions Bot enabled auto-merge May 19, 2026 21:42
@github-actions github-actions Bot merged commit 783988c into main May 19, 2026
6 checks passed
@stainless-app

stainless-app Bot commented May 19, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Release is at https://github.com/CaseMark/casedev-php/releases/tag/v0.51.0 🌻

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.

0 participants