You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
While this bumps the versions of updated packages in package.json, it does not update them in package-lock.json which necessitated PRs like this #2918
Running lerna bootstrap passing in the --package-lock-only flag documented here https://docs.npmjs.com/cli/v8/commands/npm-install, it will also update the package-lock.json files with the proper versions based on the updated package.json.
Tested this locally by creating a new changeset for a package and running npm run version which resulted in an updated package.json, changelog.md, andpackage-lock.json.
Edit to add: The lerna bootstrap -- --package-lock-only will only update the package-lock.json file if the node_modules directory for the package is empty, which it would be when this is run in the github actions pipeline. To reproduce locally, make sure the node_modules directory of the modified package is removed. Thanks @AndrewJakubowicz!
We should see this work in the next Version Release PR.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
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.
When the changeset action runs, it runs
npm run versionas it creates the Version Release PR as specified here:lit/.github/workflows/release.yaml
Line 60 in 0594bd8
While this bumps the versions of updated packages in
package.json, it does not update them inpackage-lock.jsonwhich necessitated PRs like this #2918Running
lerna bootstrappassing in the--package-lock-onlyflag documented here https://docs.npmjs.com/cli/v8/commands/npm-install, it will also update thepackage-lock.jsonfiles with the proper versions based on the updatedpackage.json.Tested this locally by creating a new changeset for a package and running
npm run versionwhich resulted in an updatedpackage.json,changelog.md, andpackage-lock.json.Edit to add: The
lerna bootstrap -- --package-lock-onlywill only update thepackage-lock.jsonfile if thenode_modulesdirectory for the package is empty, which it would be when this is run in the github actions pipeline. To reproduce locally, make sure thenode_modulesdirectory of the modified package is removed. Thanks @AndrewJakubowicz!We should see this work in the next Version Release PR.