-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump http-proxy-middleware from 2.0.6 to 2.0.7 #12341
Bump http-proxy-middleware from 2.0.6 to 2.0.7 #12341
Conversation
This one might be easier to review commit-by-commit. I removed We shouldn't be reliant on any nuxt dependencies at this point, so this dependency should be safe to remove, but it's best to validate that this is the case. |
I'll need some time to test this @rak-phillip 🙏 Not sure if I'll reply today or tomorrow |
Take your time. There's some CI failures that I need to investigate before really committing to this change. |
The removal of edit: and we're able to eliminate the |
Bumps [http-proxy-middleware](https://github.com/chimurai/http-proxy-middleware) from 2.0.6 to 2.0.7. - [Release notes](https://github.com/chimurai/http-proxy-middleware/releases) - [Changelog](https://github.com/chimurai/http-proxy-middleware/blob/v2.0.7/CHANGELOG.md) - [Commits](chimurai/http-proxy-middleware@v2.0.6...v2.0.7) --- updated-dependencies: - dependency-name: http-proxy-middleware dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
- `http-proxy-middleware@1.3.1` is a transitive dependency of `@nuxtjs/axios` - `@nuxtjs/axios` isn't used anywhere throughout shell, so it can be safely removed at this point Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
e5b999c
to
ddfb3ec
Compare
I have tested this manually by publishing shell to a local server and building the Kubewarden UI Extension using these updates. No issues were noted. I've rebased which will reapply the checks for our extensions (Kubewarden, Elemental, and NeuVector) within the check-plugins-build workflow. If this and the rest of the checks pass these changes should be fine. |
Thanks for the review @jordojordo . This was on my todo list... With the re-enable of the extension checks in the |
No problem, verdaccio is temperamental on my machine, but it worked in this case 🧙♂️ |
Bumps http-proxy-middleware from 2.0.6 to 2.0.7.
Release notes
Sourced from http-proxy-middleware's releases.
Changelog
Sourced from http-proxy-middleware's changelog.
Commits
1e92339
ci(github-actions): fix npm tag90afb7c
chore(package): v2.0.70b4274e
fix(filter): handle errors1bd6dd5
ci(github actions): add publish.ymlDependabot 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 rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will 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 version
will 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 dependency
will 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.