Chore: Update packages#40
Draft
stevensJourney wants to merge 5 commits intomainfrom
Draft
Conversation
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
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.
This bumps external dependencies, in order to avoid some warnings provided by tools such as NPMX.
An example of a recent report
The above seems to contain strange warnings. E.g. we didn't explicitly increase our dependency requirements between versions - perhaps this is related to internal dependencies. We also don't use that version of
globin our codebase.After bumping these versions, a
pnpm auditcurrently shows these itemsWhere the
cliseems to be a false match of our/clifolder, to theclipackage published to npm. Theuuidentry requires changes to the mentioned packages.TODOs:
uuidpackage in sub dependenciesAdditional Fix
As an additional fix, this fixes the release flow to build installers' artifacts in the same workflow as the release workflow (in a separate job). Currently, the
onReleaseworkflow is not triggered, due to blocked recursive Github actions invocations.