Bump fast-uri from 3.1.0 to 3.1.4 in /apps/web - #200
Conversation
Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.0 to 3.1.4. - [Release notes](https://github.com/fastify/fast-uri/releases) - [Commits](fastify/fast-uri@v3.1.0...v3.1.4) --- updated-dependencies: - dependency-name: fast-uri dependency-version: 3.1.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 54610e88a6
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "url": "https://github.com/sponsors/jonschlinkert" | ||
| } | ||
| }, | ||
| "node_modules/svelte-check/node_modules/readdirp": { |
There was a problem hiding this comment.
Restore picomatch's lockfile entry
When the Node 20 environment uses npm 11, deleting this optional-peer package makes the lockfile invalid: npm ci reports Missing: picomatch@ from lock file and exits before installing dependencies. This blocks both workflows that run npm ci after selecting an unpinned Node 20 release (.github/workflows/pr.yml and cd.yml), so retain this entry or regenerate the lockfile without dropping the picomatch peer required by svelte-check's nested fdir.
Useful? React with 👍 / 👎.
Bumps fast-uri from 3.1.0 to 3.1.4.
Release notes
Sourced from fast-uri's releases.
... (truncated)
Commits
6aeece6Bumped v3.1.42d50fbafix: reject literal backslash in URI authority0549fe3Bumped v3.1.32a6d357Merge commit from fork919dd8eBumped v3.1.2c65ba57fixup: linting6c86c17Merge commit from forka95158aHandle malformed fragment decoding without throwing (#171)cea547cBumped v3.1.1876ce79Merge commit from forkDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.