-
Notifications
You must be signed in to change notification settings - Fork 1k
[chore] Update lockfiles #2918
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[chore] Update lockfiles #2918
Conversation
π¦ Changeset detectedLatest commit: 7eff5b7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
π Tachometer Benchmark ResultsSummarynop-update
render
update
update-reflect
Resultslit-element-list
render
update
update-reflect
lit-html-kitchen-sink
render
update
nop-update
lit-html-repeat
render
update
lit-html-template-heavy
render
update
reactive-element-list
render
update
update-reflect
|
|
I don't think updating lock files needs to or really should be associated with releases. I like the idea of regularly and periodically updating dependencies. Dependabot should theoretically be doing that, but we probably need our test stabilized before automatically merging its PRs. |
justinfagnani
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
In this case we're not actually updating any dependencies. The diffs here are purely the version number of the actual package themselves. For instance, changeset updates the version in |
|
ahhh. In that case, changesets should fix and until then we definitely could :) |
Update package-lock files with version bumps that happened in the previous release.
These changes were made by running
npm run nukefrom the latest commit.Perhaps we should consider doing something like this changesets/changesets#421 (comment) to automate this.