chore: sync package-lock.json with package.json to v0.3.3 #39
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.
Hi @mcollina
After your last commit, the
package-lock.json
wasn't synced withpackage.json
.Summary
Changes synchronize the version in
package-lock.json
from0.3.2
to0.3.3
to match the current version inpackage.json
.Background
During the recent version bump to v0.3.3, the
package-lock.json
file was not fully updated, causing a version mismatch between the two package files.Changes
package-lock.json
from0.3.2
→0.3.3
package.json
andpackage-lock.json
Impact