Bump packages to 0.1.5 - #7
Merged
Merged
Conversation
core@0.1.4 was staged on npm but never approved, and the registry will not accept a publish over a staged version; app/cli 0.1.4 pin it, so republish everything as 0.1.5. Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
core@0.1.4 was staged on npm but never approved, and the registry will not
accept a publish over a staged version; app/cli 0.1.4 pin it, so republish
everything as 0.1.5.
Co-authored-by: Cursor cursoragent@cursor.com
Note
Low Risk
Version-only changes with no runtime or API modifications; risk is limited to publish/install coordination across the three packages.
Overview
Bumps the monorepo release from 0.1.4 to 0.1.5 so packages can be published again after
core@0.1.4was left in an npm staged state that blocks republishing the same version.@almond-bot/harness-studio-core,@almond-bot/harness-studio-app, andalmond-harness-studio(CLI) all move to0.1.5in theirpackage.jsonfiles, withpackage-lock.jsonupdated to match. The app pins@almond-bot/harness-studio-core@0.1.5; the CLI pins both workspace packages at 0.1.5. No application or library code changes—only version metadata and lockfile entries.Reviewed by Cursor Bugbot for commit 51f3d7d. Configure here.