Skip to content

fix: update release-please manifest to match actual version 8.6.0#1503

Merged
gjtorikian merged 1 commit intomainfrom
fix-release-please-manifest
Feb 26, 2026
Merged

fix: update release-please manifest to match actual version 8.6.0#1503
gjtorikian merged 1 commit intomainfrom
fix-release-please-manifest

Conversation

@gjtorikian
Copy link
Contributor

Description

#1499 is not quite right. Release Please is trying to change the release from 8.6 to 8.3. I'm pretty sure this is because releases went out out-of-sync with the new Release Please process.

This PR realigns the manifest to the actual released version.

Documentation

Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.

[ ] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

@gjtorikian gjtorikian requested a review from a team as a code owner February 26, 2026 20:58
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 26, 2026

Greptile Summary

This PR corrects the Release Please manifest file to reflect the actual published package version (8.6.0) instead of the stale 8.2.0 entry that was committed when the Release Please CI workflow was first introduced. Without this fix, Release Please would base its next release bump on 8.2.0 and generate a release PR that jumps forward many minor versions — out of sync with the true state of the package. The change is consistent with the current package.json version (8.6.0) and the git history, which shows version tags progressing through 8.2.0 → 8.3.0 → 8.3.1 → 8.4.0 → 8.4.1 → 8.5.0 → 8.6.0.

  • Single file changed: .release-please-manifest.json bumped from "8.2.0" to "8.6.0"
  • Root cause: The manifest was initialised at 8.2.0 when Release Please CI was added (commit 23929b6), but several releases had already landed before that automation was in place
  • No logic, security, or API surface changes — this is a pure CI/release-tooling configuration fix

Confidence Score: 5/5

  • This PR is safe to merge — it only corrects a single JSON value in a release tooling config file with no runtime impact.
  • The change is a one-line correction to a CI configuration file. The new value (8.6.0) exactly matches both package.json's "version" field and the most recent version-bump commit in the git history. There is no application code, no tests, and no API surface affected.
  • No files require special attention.

Important Files Changed

Filename Overview
.release-please-manifest.json Updates the tracked version in the Release Please manifest from 8.2.0 to 8.6.0 to align with the actual published NPM version, preventing Release Please from generating incorrect release PRs.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Git history: last real release\n8.6.0 (commit 23b1733)"] --> B["Release Please CI added\n(commit 23929b6)\nManifest initialised at 8.2.0 ❌"]
    B --> C{"Release Please reads\nmanifest = 8.2.0"}
    C -->|"Before this PR"| D["Generates release PR\nbased on 8.2.0 → wrong ❌"]
    C -->|"After this PR\nManifest = 8.6.0 ✅"| E["Generates next release PR\nbased on 8.6.0 → correct ✅"]
    E --> F["Future version bumps\naligned with actual releases"]
Loading

Last reviewed commit: 8ffde91

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 file reviewed, no comments

Edit Code Review Agent Settings | Greptile

@gjtorikian gjtorikian merged commit 6814a5c into main Feb 26, 2026
9 checks passed
@gjtorikian gjtorikian deleted the fix-release-please-manifest branch February 26, 2026 21:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants