attempt to upgrade github actions and keep coverage working

[burnettk]

upgrade actions used for coverage file artifacts.
like #948, but working

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflows, improving artifact handling and removing unused coverage upload step.

[coderabbitai]

Warning

Rate Limit Exceeded

@burnettk has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 2 minutes and 10 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

Files that changed from the base of the PR and between 84feb06 and 80bb62a.

Walkthrough

The modifications in the .github/workflows/tests.yml file reflect an effort to streamline and enhance the CI/CD pipeline's artifact handling capabilities. By removing the upload_coverage flag, the workflow simplifies its job configuration. The update to the latest versions of both the upload-artifact and download-artifact actions ensures the use of the most current features and fixes. Additionally, the inclusion of the runtime environment in the artifact name and enabling the merging of multiple artifacts aim to improve artifact management and traceability.

Changes

File	Change Summary
.github/.../tests.yml	- Removed upload_coverage flag - Updated upload-artifact to v4.3.0 - Updated download-artifact to v4.1.1 - Modified upload-artifact name to include ${{ matrix.runs-on }} - Added merge-multiple: true to download-artifact

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>.
  • Generate unit-tests for this file.
• 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 tests 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 generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 007facc and 84feb06.

Files selected for processing (1)

• .github/workflows/tests.yml (3 hunks)

Additional comments: 3

.github/workflows/tests.yml (3)

• 187-191: The upgrade of actions/upload-artifact to version v4.3.0 and the modification to include ${{ matrix.runs-on }} in the artifact name are positive changes. These adjustments enhance the artifact naming convention, making it easier to identify and manage artifacts generated from different environments. This is a good practice for CI/CD pipelines, especially in projects with multiple environments or configurations.
• 276-280: The upgrade of actions/download-artifact to version v4.1.1 and the addition of merge-multiple: true to its configuration are significant improvements. The merge-multiple: true parameter streamlines the process of working with artifacts that are split or generated across multiple jobs or workflow runs by allowing them to be merged into a single download. This change likely improves the efficiency of handling coverage data in the CI/CD pipeline.
• 187-191: The removal of the upload_coverage flag from the matrix configuration (not directly shown in the provided code but inferred from the context) and the subsequent conditional execution of the Upload coverage data step based on this flag is a critical change. It's important to ensure that the removal of this flag does not inadvertently affect the conditional logic for uploading coverage data. Verify that the coverage data is still being uploaded correctly for the intended matrix entries, especially since the conditional logic now relies on the presence of this flag.