Add automatic version updater script and github action

[barbaraperic]

Overview

Added a script that automatically updates lotus versions across filecoin-docs documentation. This helps keep our docs up-to-date without manual updates.

🚨 remove synchronize from update-versions.yml before merging. There for testing

What changed?

• Created a new script (update-versions.js) that:
  • Updates lotus version numbers in all .md files
  • Handles both lotus-x.x.x formats and standalone version numbers (example: git checkout v1.31.1)
  • you can manually run the command npm run update-version <version-number>, example npm run update-version 1.31.2
• Added GitHub Actions workflow that:
  • Runs on every open PR manually triggered
  • Fetches the latest Lotus version from GitHub releases
  • If it finds a discrepancy, it creates automated PRs with version updates

How to test?

1. Check any .md file containing a lotus version reference
2. Run the script manually: node update-versions.js <new_version>
3. Verify that all version references are updated correctly
4. Test with different version formats including:
   • Standard versions (e.g., lotus-1.31.1)
   • Version numbers without prefix
5. Change lotus version and see if github action opens a new PR with changes reflecting the new lotus version

Here is the test PR created by github action

[lanzafame]

Looks good except the miner/vx.x.x regex issue

[lanzafame]

We can remove the instructions to substitute the X.X.X for the version number, same below as well.

[barbaraperic]

done!

[ianconsolata]

Can we also add a test on all PRs that fails if the current version in the docs matches the current version in the lotus repo? That way we'll know when it gets out of date.

[barbaraperic]

Can we also add a test on all PRs that fails if the current version in the docs matches the current version in the lotus repo? That way we'll know when it gets out of date.

Great idea! We can change the github action to run on every open PR?

[smagdali]

LGTM, just need to observe that it works ok when the next lotus release happens

[ianconsolata]

Thinking about my request more, I don't think it's really necessary as long as we are diligent about merging the PRs that get opened on cron. I mostly wanted to make sure we had a test in case that cron breaks, but I think those failures will show up in the Github action logs so we're probably good.