Update CI/CD workflows and Correct Coverage

[kamiazya]

Refactor build and check workflows to improve efficiency and organization. Update artifact upload configuration. Add coverage workflow and test:coverage script. Refactor build step to use separate YAML file.

resolve #99

Summary by CodeRabbit

• New Features

  • Introduced a "Build" workflow for automating project builds.
  • Added a "Check Format and Lint" workflow to ensure code quality.
  • Implemented a "coverage" job in the CI process for better test coverage insights.
  • Configured code coverage for browser-based tests using Istanbul.

• Chores

  • Updated the Continuous Deployment (CD) process with refined build and documentation jobs.
  • Modified the Continuous Integration (CI) setup for improved efficiency and dependency management.
  • Streamlined the snapshot release process by using a separate build configuration file.

[changeset-bot]

🦋 Changeset detected

Latest commit: a7e602c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
web-csv-toolbox	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Warning

Rate Limit Exceeded

@kamiazya has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 27 minutes and 31 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 cb79fd7 and a7e602c.

Walkthrough

The project has embraced significant enhancements across its GitHub Actions workflows and configuration files, focusing on automating build processes, code quality checks, continuous deployment, and test coverage. These changes streamline development practices, ensuring consistency, efficiency, and adherence to best coding standards. With the introduction of separate YAML files for distinct tasks and the integration of coverage analysis, the project sets a robust foundation for scalable and maintainable growth.

Changes

Files	Change Summary
.github/workflows/...build.yaml, .github/workflows/pr-snapshot-release.yaml	Introduced and utilized separate YAML files for build configurations.
.github/workflows/...check.yaml	Added workflows for format checking and linting with Biome, clippy, and rustfmt for Rust projects.
.github/workflows/cd.yaml	Updated build and doc jobs, including changes in dependency installation and build steps.
.github/workflows/ci.yaml	Enhanced with a coverage job, job dependencies, Node.js setup adjustments, and artifact handling.
vite.config.ts	Configured code coverage for browser using Istanbul, including TypeScript files from src.

🐇✨
In the realm of code where the digital grass is green,
We hop through workflows, making the unseen seen.
With YAML and configs, our garden grows,
Under the moon's soft glow, our project flows.
🌙🚀

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: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between d4879a7 and cb79fd7.

Files ignored due to path filters (2)

• package.json is excluded by: !**/*.json
• pnpm-lock.yaml is excluded by: !**/*.yaml

Files selected for processing (6)

• .github/workflows/.build.yaml (1 hunks)
• .github/workflows/.check.yaml (1 hunks)
• .github/workflows/cd.yaml (3 hunks)
• .github/workflows/ci.yaml (9 hunks)
• .github/workflows/pr-snapshot-release.yaml (1 hunks)
• vite.config.ts (1 hunks)

Additional comments: 15

vite.config.ts (1)

• 49-53: The coverage configuration correctly specifies Istanbul as the provider and includes TypeScript files from the src directory. However, ensure that the all property aligns with the project's coverage goals.

.github/workflows/.build.yaml (2)

• 14-14: Ensure libstdc++-12-dev is the correct version needed for the project dependencies.
• 40-46: Excluding specific files and directories from the artifact upload is good for minimizing the artifact size. Confirm these exclusions align with the project's deployment and artifact needs.

.github/workflows/.check.yaml (3)

• 25-25: Using npx biome ci . assumes biome is available in the project's dependencies. Verify that it is correctly installed and configured.
• 46-46: Ensure cargo clippy command includes all necessary flags for the project's linting requirements.
• 50-50: The cargo fmt command is correctly used to check formatting. Ensure all Rust files are included in the formatting check.

.github/workflows/ci.yaml (5)

• 14-36: The coverage job setup is correct. Ensure the CODECOV_TOKEN secret is properly set in the repository settings.
• 5-46: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [39-55]

The Node.js testing strategy correctly tests multiple versions. Verify the matrix includes all relevant Node.js versions for the project.

• 87-92: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [81-99]

The browser testing strategy for Linux is set up correctly. Ensure the browser versions used in CI are aligned with the project's browser support policy.

• 113-118: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [104-127]

The macOS browser testing setup is appropriate. Confirm that excluding Safari is intentional and aligns with the project's testing strategy.

• 139-144: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [132-151]

The Windows browser testing setup includes Edge, which is good. Ensure the CI environment has all necessary drivers for browser testing.

.github/workflows/cd.yaml (2)

• 101-103: The documentation job correctly depends on both the build and release jobs. Confirm that this dependency chain aligns with the project's release process.
• 129-129: The pnpm build:js command for building documentation might be project-specific. Verify that this script exists and is correctly configured in package.json.

.github/workflows/pr-snapshot-release.yaml (2)

• 34-34: Using a separate YAML file for the build steps in the snapshot release workflow is a good practice for reusability. Ensure the referenced YAML file exists and is correctly configured.
• 34-34: The snapshot release workflow correctly uses the build workflow as a dependency. Ensure that the build workflow is configured to produce the necessary artifacts for the snapshot release.

[codecov]

Welcome to Codecov 🎉

Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.

Thanks for integrating Codecov - We've got you covered ☂️