chore(website): use the workspace core and server packages - #83
Merged
Merged
Conversation
The website installed @chatcops/core and @chatcops/server 0.2.0 from npm. When a release moved them out of that range, changesets rewrote the ranges and pnpm install --frozen-lockfile failed in the release run. Use workspace:^ like the widget already does, so the site always runs the code in this repo and releases don't touch its ranges.
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.
The website installed
@chatcops/coreand@chatcops/server0.2.0 from npm. In the 0.3.0 release, changesets moved those ranges to^0.3.0without updating the lockfile, sopnpm install --frozen-lockfilewould have failed in the same run that publishes 0.3.0. I worked around it by hand in #79.This switches both to
workspace:^, like the widget already is:/api/chatruns the server code from this repo (0.3.0 now) instead of 0.2.0, so retry and regenerate in the demo widget work end to endWorkers Builds already runs
pnpm -r buildfrom the root, which builds core and server before the website. No other changes.