Skip to content
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

Update dependency zaproxy to v2.0.0-rc.4 #459

Merged
merged 1 commit into from
Apr 22, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 10, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
zaproxy 2.0.0-rc.1 -> 2.0.0-rc.4 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

zaproxy/zap-api-nodejs (zaproxy)

v2.0.0-rc.4

Compare Source

Added
  • Add the API of the following add-on:
    • Custom Payloads version 0.13.0.
Changed
  • Allow to call the ZAP API with custom HTTP method (e.g. file upload).
  • Update the APIs of the following add-on:
    • Selenium version 15.16.0.
Fixed
  • Correct the HTTP method used by fileUpload core API.

v2.0.0-rc.3

Compare Source

Changed
  • Update core APIs for 2.14.

v2.0.0-rc.2

Compare Source

Changed
  • Update the link to API docs in README.md
  • Update core APIs for 2.13.
  • Update the APIs of the following add-ons:
    • AJAX Spider version 23.15.0;
    • Alert Filters version 17;
    • GraphQL Support version 0.18.0;
    • Network version 0.10.0;
    • Selenium version 15.13.0.
Fixed
  • Return errors (e.g. connection, ZAP API) with a rejected promise.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch from 67681c4 to b894369 Compare August 10, 2023 12:16
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch 6 times, most recently from dc1896f to d945a3d Compare August 14, 2023 14:02
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch 3 times, most recently from 4a6d269 to a93bd1e Compare August 22, 2023 15:27
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch 5 times, most recently from efd858f to 8cd31fc Compare September 4, 2023 11:13
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch from 8cd31fc to bba515d Compare September 19, 2023 16:03
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch 2 times, most recently from 13cc216 to 91623e2 Compare September 27, 2023 13:52
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch from 91623e2 to 06185ec Compare October 14, 2023 15:28
@renovate renovate bot changed the title Update dependency zaproxy to v2.0.0-rc.2 Update dependency zaproxy to v2.0.0-rc.3 Oct 14, 2023
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch 7 times, most recently from 7e9b482 to a30eb76 Compare October 19, 2023 12:52
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch 2 times, most recently from 0594983 to 4598e53 Compare November 3, 2023 16:00
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch 5 times, most recently from 114d94a to 7ed8755 Compare March 26, 2024 14:19
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch from 7ed8755 to 03838eb Compare March 26, 2024 15:14
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch 6 times, most recently from 9266d58 to 2c8b22a Compare April 11, 2024 13:08
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch 3 times, most recently from a57b1b6 to c5baa65 Compare April 11, 2024 13:37
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch 8 times, most recently from 05f97ba to aa56559 Compare April 18, 2024 09:53
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch from aa56559 to 90e9f49 Compare April 22, 2024 09:47
@renovate renovate bot force-pushed the renovate/zaproxy-2.x-lockfile branch from 90e9f49 to 4b3bf7d Compare April 22, 2024 13:39
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@cshnimble cshnimble merged commit 6dd98a9 into master Apr 22, 2024
2 checks passed
@cshnimble cshnimble deleted the renovate/zaproxy-2.x-lockfile branch April 22, 2024 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants