GitHub Build Failing with: The following actions uses node12 which is deprecated

[valhuber]

Context

No response

Bug description

Pushing a minor change to my docs resulted in the following GitHub build error from the doc auto-build:

[deploy](https://github.com/ApiLogicServer/Docs/actions/runs/6607804942/job/17945648585)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

When I look up the GitHub link, it says to update this, but there is no such entry in my workflow:

runs:
  using: 'node20'
  main: 'main.js'

Various stackoverflow entries suggested updating the requirements.txt, which I believe is now current.

My Doc Site is: https://github.com/ApiLogicServer/Docs.

Here is the workflow, which was built by following the doc'd procedures (years ago, don't recall where I got it).

I am happy to open the repo so you can issue a build if that proves necessary.

Related links

• Reporting a bug

Reproduction

This happens on a push into the docs repp.

Steps to reproduce

1. Update an md file and push
2. Observe failure (images attached)

Browser

No response

Before submitting

• I have read and followed the bug reporting guidelines.
• I have attached links to the documentation, and possibly related issues and discussions.
• I assure that I have removed all customizations before submitting this bug report.
• I have attached a .zip file with a minimal reproduction.

Browser

No response

Before submitting

• I have read and followed the bug reporting guidelines.
• I have attached links to the documentation, and possibly related issues and discussions.
• I assure that I have removed all customizations before submitting this bug report.
• I have attached a .zip file with a minimal reproduction.

[squidfunk]

Thanks for reporting. I'm not sure where this is coming from, but we are not advertising use of Node.js in any of our guides. I'm converting this to a discussion, since this seems to be a general problem. Additionally, no reproduction was provided, so nothing we can look into.

[squidfunk]

Well, as the error message says, you need to update actions/cache:

uses: actions/cache@v3

[valhuber]

Made that change. Now fails with "exit 1"

[squidfunk]

Please read the stack trace... it says that there are unrecognized links and you're building in strict mode, so any warning fails the build. If you fix the links, the build will succeed. I recommend doing this locally, much easier than going through CI every time.

[valhuber]

All set. I use local all the time. I did not realize it was failing due to (in my scramble) I had updated from medics 1.4. to 1.5 (the change to the link format).

…

On Oct 24, 2023, at 8:59 AM, Martin Donath ***@***.***> wrote: Please read the stack trace... it says that there are unrecognized links and you're building in strict mode, so any warning fails the build. If you fix the links, the build will succeed. I recommend doing this locally, much easier than going through CI every time. — Reply to this email directly, view it on GitHub <#6237 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKSG352VHZD5IRBK6G47MDYA7QUXAVCNFSM6AAAAAA6N5ELW2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TGNZRHE2DG>. You are receiving this because you authored the thread.