Skip to content
Linters

fix: patch to edit escaped characters in content field #520

Sign in to view logs

fix: patch to edit escaped characters in content field

fix: patch to edit escaped characters in content field #520

Triggered via pull request October 15, 2024 15:39
@AyshaHakeemAyshaHakeem
opened #288
AyshaHakeem:wiki-fix
Status Success
Total duration 2m 46s
Artifacts –

linters.yml

on: pull_request
Semantic Commits
16s
Semantic Commits
Frappe Linter
2m 33s
Frappe Linter
Vulnerable Dependency Check
8s
Vulnerable Dependency Check
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Vulnerable Dependency Check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Semantic Commits
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Frappe Linter
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/