Skip to content

Conversation

@wraithgar
Copy link
Member

When we update the trees, the edges are refreshed to correct their
specs. If we have written the package-lock before this point, it will
be incorrect.

No new tests are needed as existing tests were snapshotted w/ the broken
behavior, and are fixed now showing this bugfix in action.

A potential unhandled exception was removed when the promises array was being made, but only awaited after the for loop was done.

Finally, there was a spurious snapshot that I also removed before changing any code so that the fix commit could only show the bugfix changes.

When we update the trees, the edges are refreshed to correct their
specs.  If we have written the package-lock before this point, it will
be incorrect.

No new tests are needed as existing tests were snapshotted w/ the broken
behavior, and are fixed now showing this bugfix in action.
@wraithgar wraithgar requested a review from a team as a code owner January 26, 2023 20:32
@wraithgar
Copy link
Member Author

Closes #5587

@fritzy fritzy merged commit 72a7a59 into latest Feb 1, 2023
@fritzy fritzy deleted the gar/workspace-dep-lock-version branch February 1, 2023 22:03
@github-actions github-actions bot mentioned this pull request Feb 1, 2023
@github-actions github-actions bot mentioned this pull request Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants