ci: disable lts/*

[TobiTenno]

Summary
turn off lts/* run

---

Resolves issue
closes #

---

Screenshots/examples

Summary by CodeRabbit

• Chores
  • Updated CI workflow to streamline testing with specific Node.js versions.
  • Added necessary package installations to the workflow.
  • Maintained caching for dependencies across jobs.
  • Improved linting process for better code quality.

[coderabbitai]

Walkthrough

The changes in the GitHub Actions workflow configuration file .github/workflows/ci.yaml involve updates to the test job's strategy matrix, specifically removing the 'lts/*' entry while retaining versions '20' and '18'. Comments have been added for clarity. The install job now includes specific package installations and maintains a caching mechanism for node_modules. The lint job has been organized to run linters and commitlint based on the pull request's commit range. These modifications aim to streamline the testing and installation processes.

Changes

File	Change Summary
.github/workflows/ci.yaml	- Modified test job's strategy matrix: removed 'lts/*', kept '20' and '18', added comments.
	- Updated install job to include warframe-worldstate-parser@^4.x and warframe-worldstate-data@^2.x.
	- Retained caching for node_modules across jobs.
	- Structured lint job to run linters and commitlint using the pull request's commit range.

Sequence Diagram(s)

sequenceDiagram
    participant CI as CI Workflow
    participant Install as Install Job
    participant Test as Test Job
    participant Lint as Lint Job
    participant Cache as Cache Mechanism

    CI->>Install: Start Install Job
    Install->>Cache: Cache node_modules
    Install->>Install: npm install warframe-worldstate-parser@^4.x, warframe-worldstate-data@^2.x
    CI->>Test: Start Test Job
    Test->>Cache: Use cached node_modules
    CI->>Lint: Start Lint Job
    Lint->>Lint: Run linters and commitlint

Loading

🐰 "In the CI's dance, we streamline our way,
With versions in line, we brighten the day.
Packages installed, our cache stays so neat,
Linting and testing, oh, what a treat!
Let's hop through the code, with joy and with cheer,
For every small change, a victory near!" 🐇✨

Warning

Rate limit exceeded

@TobiTenno has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 24 minutes and 56 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 8410311 and ef92ccf.

---

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.

[codeclimate]

Code Climate has analyzed commit ef92ccf and detected 0 issues on this pull request.

View more on Code Climate.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8410311 and ef92ccf.

📒 Files selected for processing (1)

• .github/workflows/ci.yaml (1 hunks)