Skip to content

build(deps): bump zaproxy/action-baseline from 0.12.0 to 0.15.0 - #1

Open
dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/github_actions/zaproxy/action-baseline-0.15.0
Open

build(deps): bump zaproxy/action-baseline from 0.12.0 to 0.15.0#1
dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/github_actions/zaproxy/action-baseline-0.15.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 30, 2026

Copy link
Copy Markdown

Bumps zaproxy/action-baseline from 0.12.0 to 0.15.0.

Release notes

Sourced from zaproxy/action-baseline's releases.

Version 0.15.0

Changed

  • Update dependencies.
  • Run with node24.

Version 0.14.0

Changed

  • Update dependencies to stop using deprecated upload-artifact version.

Version 0.13.0

Changed

  • Update dependencies, which adds rate-limiting when accessing the GitHub API.

Fixed

  • Allow to write any file from the Docker container. #118
Changelog

Sourced from zaproxy/action-baseline's changelog.

Changelog

All notable changes to this GitHub action will be documented in this file.

The format is based on Keep a Changelog.

[Unreleased]

Changed

Update dependencies.

[0.15.0] - 2025-10-22

Changed

  • Update dependencies.
  • Run with node24.

[0.14.0] - 2024-11-20

Changed

  • Update dependencies to stop using deprecated upload-artifact version.

[0.13.0] - 2024-09-25

Changed

  • Update dependencies, which adds rate-limiting when accessing the GitHub API.

Fixed

  • Allow to write any file from the Docker container. #118

[0.12.0] - 2024-04-02

Changed

  • Update dependencies.

[0.11.0] - 2024-01-25

Changed

  • Run with node20. #114

[0.10.0] - 2023-10-31

Added

  • Support for authentication environment variables.

Fixed

  • Update Crowdin link.

[0.9.0] - 2023-08-02

Changed

  • The default Docker image was changed to ghcr.io/zaproxy/zaproxy:stable.

[0.8.2] - 2023-07-04

Fixed

  • Fix an issue introduced in the previous release that prevented the use of the default GitHub authentication token to raise issues.

[0.8.1] - 2023-07-03

Fixed

... (truncated)

Commits
  • de8ad96 Merge pull request #143 from thc202/release-v0.15.0
  • f5ca774 Release v0.15.0
  • 5518416 Merge pull request #142 from zaproxy/dependabot/npm_and_yarn/brace-expansion-...
  • e429174 Bump brace-expansion from 1.1.11 to 1.1.12
  • 85f1db6 Merge pull request #141 from thc202/nodejs24
  • e525ed6 Bump Node.js and update dependencies
  • aeed8ca Merge pull request #137 from zaproxy/dependabot/npm_and_yarn/octokit/endpoint...
  • b57022e Update dist file and changelog
  • 1374ee7 Bump @​octokit/endpoint from 10.1.1 to 10.1.4
  • adc29ad Merge pull request #136 from zaproxy/dependabot/npm_and_yarn/babel/helpers-7....
  • Additional commits viewable in compare view

@dependabot @github

dependabot Bot commented on behalf of github Jul 30, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: ci, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

votrongdao added a commit that referenced this pull request Aug 2, 2026
The failure was one line — "mermaid diagram failed to parse" — for a sweep over
seventy-odd diagrams. The file was carried as `file=` on the annotation, which
renders against the file in the web UI and does not appear in the log at all, so
anyone reading the log got the fact that something somewhere was broken. The
parser's own message, which names the line and the token it choked on, was
redirected to /dev/null. Finding the diagram meant installing mermaid-cli locally
and bisecting.

Now the log body names the file and the diagram's index within it, prints the
diagram, and prints what mermaid said, minus the puppeteer stack frames that are
never the document's fault.

Scope widened from `find docs samples -name '*.md'` to `git ls-files '*.md'`.
Diagrams in PLAN.md and in READMEs outside those two trees render on the same
GitHub pages as the rest and were checked by nothing — the same "gate whose
subject is absent" shape as the 166 skipped tests. Every tracked markdown file
now parses except the one named below, and `git ls-files` cannot wander into
node_modules or a bin/ directory the way a bare `find` would.

Verified by extracting this step from the workflow and running it against the
tree: it reports exactly one failure, samples/banking/README.md diagram #1, with
the diagram and mermaid's "Parse error on line 16" beneath it.

The diagram itself is NOT fixed here. samples/banking belongs to another change in
flight and this branch does not write to it. The defect is a semicolon inside a
`Note over` line: mermaid treats `;` as a statement separator, so the note ends at
"allows five" and "see below" is parsed as a statement and is not one. Replacing
that one character with a comma renders the diagram — checked, 29,205 bytes of
SVG. It is a one-character change on README.md line 190 for whoever holds that
tree, and until it lands this job stays red.
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/zaproxy/action-baseline-0.15.0 branch from 03c1729 to 88715c8 Compare August 5, 2026 10:58
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown

Coverage thresholds — the test step failed, not the thresholds.

::error::FlowX.Conformance.TheSuiteRejectsAProcessLocalLimiterTests.ANonAtomicClaimFailsConcurrentCallersOfOneKeyProduceExactlyOneClaim
Shouldly.ShouldAssertException : failure
    should not be null but was

Additional Info:
    ConcurrentCallersOfOneKeyProduceExactlyOneClaim passed against a store that violates the guarantee it describes. A suite that accepts a store it was written to reject is not a gate.
1 failed test(s) named across 28 trx file(s).

Bumps [zaproxy/action-baseline](https://github.com/zaproxy/action-baseline) from 0.12.0 to 0.15.0.
- [Release notes](https://github.com/zaproxy/action-baseline/releases)
- [Changelog](https://github.com/zaproxy/action-baseline/blob/master/CHANGELOG.md)
- [Commits](zaproxy/action-baseline@66042c8...de8ad96)

---
updated-dependencies:
- dependency-name: zaproxy/action-baseline
  dependency-version: 0.15.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/zaproxy/action-baseline-0.15.0 branch from 88715c8 to 045c12b Compare August 9, 2026 08:26
@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown

Coverage thresholds — the test step failed, not the thresholds.

::error::FlowX.Redis.Tests.RedisLeaseStoreTests.TheLeaseKeyNeverCarriesARedisExpiry
Shouldly.ShouldAssertException : renewed.IsSuccess
    should be
True
    but was
False
1 failed test(s) named across 28 trx file(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants