Changed expired nodes to latest ones

[fischuu]

When I tried to create a GitHub action with this script, I got errors and had to update to version 4 in both places to get it running error free

Summary by CodeRabbit

• Chores
  • Updated CI/CD pipeline actions to newer versions for improved performance and reliability.

[coderabbitai]

Walkthrough

The pull request updates the versions of two GitHub Actions in the CI/CD pipeline as specified in the README.md file. The actions/checkout action is upgraded from version v2 to v4, and the github/super-linter action is upgraded from version v3 to v4. These updates reflect a transition to more recent versions of these actions.

Changes

File	Change Summary
README.md	Updated actions/checkout from v2 to v4 and github/super-linter from v3 to v4.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 4a92aea and 70b5f47.

📒 Files selected for processing (1)

• README.md (1 hunks)

🔇 Additional comments not posted (3)

README.md (3)

328-328: Approved: actions/checkout version update

The update from actions/checkout@v2 to actions/checkout@v4 is a good practice to keep your GitHub Actions workflow up-to-date. This change aligns with the PR objective of updating expired nodes to the latest ones.

To ensure a smooth transition, please verify that there are no breaking changes in v4 that might affect your workflow. You can check the changelog at: https://github.com/actions/checkout/blob/main/CHANGELOG.md

---

331-331: Approved: github/super-linter version update

The update from github/super-linter@v3 to github/super-linter@v4 is a positive change that keeps your linting workflow current. This aligns well with the PR objective of updating expired nodes to the latest versions.

To ensure a smooth transition and potentially leverage new features:

1. Please review the changelog at: https://github.com/github/super-linter/blob/main/CHANGELOG.md
2. Check for any breaking changes or new configuration options that might benefit your project.
3. Verify that all existing linter configurations are still compatible with v4.

---

328-331: Summary of GitHub Actions updates

The changes in this PR are focused and align well with the objective of updating expired nodes to the latest versions. Both actions/checkout and github/super-linter have been updated from their previous versions to v4. These updates are likely to bring improvements in functionality, security, and performance to your CI/CD pipeline.

To ensure a smooth transition:

1. Test the updated workflow thoroughly to catch any potential issues early.
2. Monitor the first few runs of the updated workflow in your repository to ensure everything works as expected.
3. Consider documenting these version updates in your project's changelog or release notes.

Overall, these changes represent good maintenance practices and should be beneficial for the project.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.