Bump launch-editor from 2.8.1 to 2.14.1 - #4994
Conversation
Bumps [launch-editor](https://github.com/vitejs/launch-editor) from 2.8.1 to 2.14.1. - [Commits](vitejs/launch-editor@v2.8.1...v2.14.1) --- updated-dependencies: - dependency-name: launch-editor dependency-version: 2.14.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Up to standards ✅🟢 Issues
|
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull Request Overview
The pull request intended to upgrade 'launch-editor' from 2.8.1 to 2.14.1; however, the provided diff is currently empty. The expected updates to 'package.json' are missing, meaning the primary acceptance criteria for this dependency bump have not been met. While the automated quality analysis reports the PR is up to standards, this is a result of having no code changes to evaluate. The PR cannot be merged in its current state as it lacks the actual version update.
About this PR
- The pull request does not contain any file changes. The expected update to 'package.json' to bump 'launch-editor' to 2.14.1 is missing. Please ensure the changes are committed and pushed correctly.
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
Bumps launch-editor from 2.8.1 to 2.14.1.
Commits
3f97c64v2.14.10cc9550fix: reject UNC paths (#138)afd1ab9ci: run tests on mac and windows (#136)0bfa328test: add some tests for launch-editor package (#135)1b006aechore: add README (#134)383ef26v2.14.06277209ci: harden publish settings520b2f7fix(deps): update all non-major dependencies (#129)475ac66chore(deps): update dependency lint-staged to v17 (#130)247bf1dchore(deps): update dependency yorkie to v2 (#131)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for launch-editor since your current version.
Dependabot 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.