Skip to content

chore(doc): fix 'how to upgrade fury' link in README (#1846) #1

chore(doc): fix 'how to upgrade fury' link in README (#1846)

chore(doc): fix 'how to upgrade fury' link in README (#1846) #1

Triggered via push September 18, 2024 08:48
Status Success
Total duration 20s
Artifacts

lint.yml

on: push
🍇 Markdown
8s
🍇 Markdown
🍏 YAML
6s
🍏 YAML
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
🍏 YAML
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3.1.0, actions/setup-python@v4.1.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
🍏 YAML
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
🍏 YAML
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
🍏 YAML: .github/workflows/ci.yml#L165
165:49 [comments] too few spaces before comment
🍏 YAML: .github/workflows/ci.yml#L181
181:49 [comments] too few spaces before comment
🍇 Markdown
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3.1.0, 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/