Fix failing installation on Linux and Refactor Main Workflow

[kamiazya]

Update workflow.yaml to include new jobs for checks, unit tests, build, and integration test.

And cache clear before apt-get update.

Background

This implemented an integration test that actually executes the GitHub Action.

Initially, the goal was to diagnose the cause of failures occurring when running GitHub Actions on macOS. Fortunately, I managed to install Graphviz on macOS without any alterations to the existing mechanisms. (#593)

However, during this process, I encountered new issues with installations on Linux. As a temporary measure, I have implemented provisional support using apt-get.

fix #593
fix #601

Summary by CodeRabbit

• Chores

  • Updated GitHub Actions workflows to use newer versions of actions for improved reliability and performance.

• New Features

  • Added a new script for TypeScript type checking without file emission.

• Refactor

  • Improved workflow structure with separate jobs for various checks and tests in the CI/CD pipeline.
  • Enhanced the installation process in GraphvizInstaller to clean up system caches more efficiently before updates.

[coderabbitai]

Walkthrough

This update enhances GitHub Actions workflows by using updated action versions and refines the workflow structure with distinct jobs for various testing phases. Additionally, a new TypeScript script for type checking is introduced in package.json, and improvements are made to the GraphvizInstaller class and its tests, optimizing the installation process and system updates handling.

Changes

Files	Change Summary
.github/workflows/release.yaml, .github/workflows/update-license-year.yaml	Updated GitHub Actions to newer versions.
.github/workflows/workflow.yaml	Improved workflow structure with separate jobs for checks, tests, and builds.
package.json	Added "typecheck" script for TypeScript type checking.
src/GraphvizInstaller.ts, src/__tests__/GraphvizInstaller.spec.ts	Enhanced GraphvizInstaller operations and corresponding tests, focusing on system updates and package installations.

Poem

🐰🌟
In the land of code and might,
A rabbit hopped through the night.
With a flick of its tiny paw,
Bugs were fixed, and awe was saw.
Cheers to updates, clean and bright!
🌟🐰

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d1cba3a and 1107b27.

Files selected for processing (6)

• .github/workflows/release.yaml (1 hunks)
• .github/workflows/update-license-year.yaml (1 hunks)
• .github/workflows/workflow.yaml (1 hunks)
• package.json (1 hunks)
• src/GraphvizInstaller.ts (1 hunks)
• src/tests/GraphvizInstaller.spec.ts (7 hunks)

Files skipped from review due to trivial changes (2)

• .github/workflows/release.yaml
• .github/workflows/update-license-year.yaml

Additional comments not posted (4)

package.json (1)

16-16: The addition of the "typecheck": "tsc --noEmit" script is a good enhancement for development, allowing type checks without file emission.

src/GraphvizInstaller.ts (1)

37-44: The addition of apt cache cleaning and removal of the Microsoft product list file before updating apt repositories is a good practice for ensuring a clean environment. Please verify the necessity and potential impacts of removing the Microsoft product list file.

.github/workflows/workflow.yaml (1)

4-88: The restructuring of the workflow into separate jobs for checks, unit tests, build, and integration tests, along with the use of specific versions for GitHub Actions, enhances the clarity and reliability of the CI process.

src/__tests__/GraphvizInstaller.spec.ts (1)

160-199: > 📝 NOTE

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

The updates to the test commands align well with the changes in the GraphvizInstaller class. The use of inline snapshots for verifying command executions is an effective testing practice.

---

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 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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.
• 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.