Skip to content

Commit 478e1e1

Browse files
chore(deps): bump DavidAnson/markdownlint-cli2-action (#3923)
* chore(docs): address `no-generic-link-test` lint (#3923) this addresses errors observed by dependabot when upgrading to the latest version of `markdownlint`. there is a new lint, added in DavidAnson/markdownlint#1459, that introduces forbidden link text to discourage generic `here` text in links. this fixes sentences that included a link labeled "here". * #3918 * https://github.com/linkerd/linkerd2-proxy/actions/runs/15043224730/job/42279610780?pr=3918 * https://github.com/DavidAnson/markdownlint/blob/v0.38.0/doc/md059.md * DavidAnson/markdownlint#1459 * DavidAnson/markdownlint#681 ``` Summary: 3 error(s) Error: docs/FUZZING.md:17:13 MD059/descriptive-link-text Link text should be descriptive [Context: "[here]"] https://github.com/DavidAnson/markdownlint/blob/v0.38.0/doc/md059.md Error: docs/FUZZING.md:100:2 MD059/descriptive-link-text Link text should be descriptive [Context: "[here]"] https://github.com/DavidAnson/markdownlint/blob/v0.38.0/doc/md059.md Error: README.md:90:2 MD059/descriptive-link-text Link text should be descriptive [Context: "[here]"] https://github.com/DavidAnson/markdownlint/blob/v0.38.0/doc/md059.md Error: Failed with exit code: 1 ``` Signed-off-by: katelyn martin <kate@buoyant.io> * build(deps): bump DavidAnson/markdownlint-cli2-action (#3923) Bumps [DavidAnson/markdownlint-cli2-action](https://github.com/davidanson/markdownlint-cli2-action) from 19.1.0 to 20.0.0. - [Release notes](https://github.com/davidanson/markdownlint-cli2-action/releases) - [Commits](DavidAnson/markdownlint-cli2-action@05f3221...992badc) --- updated-dependencies: - dependency-name: DavidAnson/markdownlint-cli2-action dependency-version: 20.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> --------- Signed-off-by: katelyn martin <kate@buoyant.io> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
1 parent 1eeae37 commit 478e1e1

File tree

3 files changed

+12
-9
lines changed

3 files changed

+12
-9
lines changed

.github/workflows/markdown.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,6 @@ jobs:
1515
runs-on: ubuntu-24.04
1616
steps:
1717
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
18-
- uses: DavidAnson/markdownlint-cli2-action@05f32210e84442804257b2a6f20b273450ec8265
18+
- uses: DavidAnson/markdownlint-cli2-action@992badcdf24e3b8eb7e87ff9287fe931bcb00c6e
1919
with:
2020
globs: "**/*.md"

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -86,8 +86,9 @@ minutes to review our [code of conduct][coc].
8686
We test our code by way of fuzzing and this is described in [FUZZING.md](/docs/FUZZING.md).
8787

8888
A third party security audit focused on fuzzing Linkerd2-proxy was performed by
89-
Ada Logics in 2021. The full report is available
90-
[here](/docs/reports/linkerd2-proxy-fuzzing-report.pdf).
89+
Ada Logics in 2021. The
90+
[full report](/docs/reports/linkerd2-proxy-fuzzing-report.pdf) can be found in
91+
the `docs/reports/` directory.
9192

9293
## License
9394

docs/FUZZING.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,12 @@ engine.
1212
We place the fuzz tests into folders within the individual crates that the fuzz
1313
tests target. For example, we have a fuzz test that that target the crate
1414
`/linkerd/addr` and the code in `/linkerd/addr/src` and thus the fuzz test that
15-
targets this crate is put in `/linkerd/addr/fuzz`. The folder set up we use for
16-
each of the fuzz tests is automatically generated by `cargo fuzz init`
17-
(described [here](https://github.com/rust-fuzz/cargo-fuzz#cargo-fuzz-init)).
15+
targets this crate is put in `/linkerd/addr/fuzz`.
16+
17+
The folder structure for each of the fuzz tests is automatically generated by
18+
`cargo fuzz init`. See cargo fuzz's
19+
[`README.md`](https://github.com/rust-fuzz/cargo-fuzz#cargo-fuzz-init) for more
20+
information.
1821

1922
### Fuzz targets
2023

@@ -96,6 +99,5 @@ unit-test-like fuzzers, but are essentially just more substantial in nature. The
9699
idea behind these fuzzers is to test end-to-end concepts more so than individual
97100
components of the proxy.
98101

99-
The inbound fuzzer
100-
[here](/linkerd/app/inbound/fuzz/fuzz_targets/fuzz_target_1.rs) is an example of
101-
this.
102+
The [inbound fuzzer](/linkerd/app/inbound/fuzz/fuzz_targets/fuzz_target_1.rs)
103+
is an example of this.

0 commit comments

Comments
 (0)