Skip to content

chore(main): release deploygate 1.5.0#29

Merged
tnj merged 2 commits into
mainfrom
release-please--branches--main--components--deploygate
Jun 1, 2026
Merged

chore(main): release deploygate 1.5.0#29
tnj merged 2 commits into
mainfrom
release-please--branches--main--components--deploygate

Conversation

@deploygate-release-please-bot
Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.5.0 (2026-06-01)

Features

  • expose the full DeployGate public API as MCP tools (apps, projects, workspaces) (#27) (60b288d)

This PR was generated with Release Please. See documentation.

@tnj tnj merged commit 4ee26e9 into main Jun 1, 2026
3 checks passed
@tnj tnj deleted the release-please--branches--main--components--deploygate branch June 1, 2026 07:48
@deploygate-release-please-bot
Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

tnj added a commit that referenced this pull request Jun 1, 2026
#32)

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>
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