Skip to content

chore(main): release 6.0.1#384

Open
workos-sdk-automation[bot] wants to merge 1 commit intomainfrom
release-please--branches--main--components--workos/workos-php
Open

chore(main): release 6.0.1#384
workos-sdk-automation[bot] wants to merge 1 commit intomainfrom
release-please--branches--main--components--workos/workos-php

Conversation

@workos-sdk-automation
Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

6.0.1 (2026-05-06)

Miscellaneous Chores

  • release: include v prefix in tags (5517b8b)

This PR was generated with Release Please. See documentation.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented May 6, 2026

Greptile Summary

Automated patch release bumping the SDK from 6.0.0 to 6.0.1, generated by Release Please. The sole underlying change is a fix to include the v prefix in release tags.

  • .release-please-manifest.json and lib/Version.php: version string updated from 6.0.0 to 6.0.1.
  • CHANGELOG.md: new 6.0.1 entry added documenting the v-prefix tag fix.

Confidence Score: 5/5

Safe to merge — all three files are mechanical version-string updates with no logic changes.

Every change is a version string replacement driven by Release Please automation: the manifest JSON, the PHP constant, and the changelog entry. No functional code is touched.

No files require special attention.

Important Files Changed

Filename Overview
.release-please-manifest.json Version field bumped from 6.0.0 to 6.0.1 by Release Please automation
CHANGELOG.md New 6.0.1 changelog entry added describing the v-prefix tag fix
lib/Version.php SDK_VERSION constant updated from 6.0.0 to 6.0.1; no logic changes

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release Please Bot] -->|Detects v-prefix tag fix commit| B[Bump version 6.0.0 → 6.0.1]
    B --> C[Update .release-please-manifest.json]
    B --> D[Update lib/Version.php SDK_VERSION]
    B --> E[Append CHANGELOG.md entry]
Loading

Reviews (1): Last reviewed commit: "chore(main): release 6.0.1" | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

0 participants