chore: revert deploygate 1.5.0 release to restore 1.4.0 released state#32
Merged
Conversation
The 1.5.0 release (#29) created the git tag and GitHub Release, but the npm publish step failed (broken lockfile, fixed separately in #30), so 1.5.0 was never published to npm. Deleting the v1.5.0 tag/Release to retrigger publishing instead corrupted release-please's baseline (manifest said 1.5.0 with no matching tag), causing it to propose a bogus 1.3.1 downgrade. Revert the 1.5.0 version bump and CHANGELOG entry so the manifest (1.4.0) matches the existing deploygate--v1.4.0 tag. This restores a consistent "1.4.0 released" baseline; release-please will then re-propose 1.5.0 cleanly from the feature commits since v1.4.0, and the publish will run with the fixed lockfile (#30, retained here). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request reverts the project version from 1.5.0 back to 1.4.0 across several configuration and manifest files, including package.json, package-lock.json, and plugin configurations, while also removing the 1.5.0 release notes from the changelog. There are no review comments, and I have no feedback to provide.
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
1 participant
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.
Background
The 1.5.0 release (#29) created the git tag
deploygate--v1.5.0and the GitHub Release, but thenpm publishstep failed because the lockfile committed in #26 was missing esbuild's optional platform packages (fixed in #30). As a result, 1.5.0 was never published to npm.Deleting the v1.5.0 tag and GitHub Release to retrigger publishing then corrupted release-please's baseline: the manifest still said
1.5.0but no matching tag existed, so release-please proposed a bogus 1.5.0 -> 1.3.1 downgrade PR (#31, now closed).What this PR does
Reverts the 1.5.0 release commit (#29): resets the manifest and all version files back to
1.4.0and removes the 1.5.0 CHANGELOG entry. The lockfile fix from #30 is retained (all 26@esbuild/*platform entries are still present).This restores a consistent "1.4.0 released" baseline where the manifest (
1.4.0) matches the existingdeploygate--v1.4.0tag.After merge
release-please will re-propose 1.5.0 cleanly from the feature commit (#27) since v1.4.0. Merging that fresh release PR will run the publish path with the fixed lockfile, so
@deploygate/mcp@1.5.0finally lands on npm.Verified
npm cipasses under npm 11 (npm ci --dry-runsucceeds).🤖 Generated with Claude Code