feat: change skia-canvas to github release

[ltxhhz]

closes #710

Summary by CodeRabbit

• New Features

  • Updated the distribution URL for the skia-canvas binary to enhance accessibility.

• Bug Fixes

  • Adjusted the configuration for requiredNapiVersions for the skia-canvas binary, streamlining its usage.

[coderabbitai]

Walkthrough

The changes in this pull request involve updates to the config/binaries.ts file, specifically for the skia-canvas binary. The distUrl has been modified to point to a new location on GitHub for releases. Additionally, the requiredNapiVersions property within the options for this binary has been commented out, indicating a change in its necessity or usage. No other binaries were affected by these modifications.

Changes

File	Change Summary
config/binaries.ts	Updated distUrl for skia-canvas from https://skia-canvas.s3.us-east-1.amazonaws.com to https://github.com/samizdatco/skia-canvas/releases; commented out requiredNapiVersions in options for skia-canvas.

Poem

In the land of code where rabbits play,
A new path for skia-canvas leads the way.
From S3 to GitHub, a hop and a skip,
With options refined, we take a new trip.
Let's celebrate changes, both big and small,
For in our code garden, there's room for us all! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 44ca113 and 9f34460.

📒 Files selected for processing (1)

• config/binaries.ts (1 hunks)

🧰 Additional context used

🔇 Additional comments (1)

config/binaries.ts (1)

139-142: Review changes to skia-canvas configuration

The changes to the skia-canvas configuration look good overall, but there are a couple of points to consider:

1. The distUrl has been updated to use the official GitHub releases page instead of a custom S3 bucket. This is generally a good practice as it ensures we're using the official distribution channel.

2. The requiredNapiVersions option has been commented out. While this might allow for broader compatibility, it could potentially lead to unexpected behavior if the binary relies on specific Node.js API versions.

To ensure these changes don't introduce any issues, please run the following verification steps:

Additionally, it would be beneficial to test this change with different Node.js versions to ensure compatibility hasn't been affected by commenting out requiredNapiVersions.

---

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.

[fengmk2]

合并到 #715