Update dependency zaproxy to v2.0.0-rc.4 #360
Merged
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
3 times, most recently
from
618a558 to
964fdfe
Compare
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
2 times, most recently
from
bde8afd to
3fa67dc
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
5 times, most recently
from
8f3835c to
bd56bf5
Compare
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
4 times, most recently
from
a643061 to
5291970
Compare
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
2 times, most recently
from
111d6d4 to
66416d3
Compare
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
6 times, most recently
from
004f79b to
87ee818
Compare
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
3 times, most recently
from
80951d9 to
6941f43
Compare
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
3 times, most recently
from
e04f73e to
32ad6e1
Compare
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
from
32ad6e1 to
7e18689
Compare
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
4 times, most recently
from
dd20dc8 to
3423203
Compare
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
10 times, most recently
from
7947524 to
b77b7e6
Compare
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
3 times, most recently
from
bf07e40 to
c521eee
Compare
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
5 times, most recently
from
202f779 to
fa36dbf
Compare
cshnimble
approved these changes
Apr 17, 2024
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
2 times, most recently
from
7ceb35d to
8941e1a
Compare
renovate
bot
force-pushed
the
renovate/zaproxy-2.x-lockfile
branch
from
8941e1a to
2826895
Compare
|
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 PR contains the following updates:
2.0.0-rc.2->2.0.0-rc.4Warning
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.4Compare Source
Added
Changed
Fixed
fileUploadcore API.v2.0.0-rc.3Compare Source
Changed
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.
This PR has been generated by Mend Renovate. View repository job log here.