:coffee: Add `denops/supported-versions.json` and check if all information is updated

lambdalisue commented 1 month ago

To solve https://github.com/vim-denops/deno-denops-std/issues/249

Summary by CodeRabbit

New Features
- Introduced a new task to manage supported versions more easily within the Deno environment.
- Added dynamic loading of supported versions for Deno, Vim, and Neovim, improving flexibility and maintainability.
Enhancements
- Updated GitHub Actions workflow to check for version inconsistencies, ensuring compatibility during CI processes.
- Automated updates to documentation and configuration files to reflect current supported versions.
New Files
- Added a JSON file to specify supported versions of Deno, Vim, and Neovim, enhancing application robustness.

coderabbitai[bot] commented 1 month ago

Walkthrough

This update introduces significant improvements to a Deno project’s workflow and version management. Key changes include enhanced GitHub Actions for version consistency checks, a new script for updating version references across documentation, and dynamic version loading in Vim scripts. Additionally, a new Deno task simplifies applying supported version updates, backed by a JSON configuration file detailing compatible versions. These enhancements collectively bolster the project's maintainability and clarity.

Changes

Files	Change Summary
`.github/workflows/test.yml`	Updated job matrix to use `deno_version`, fixed version string, added version inconsistency check.
`.scripts/apply_supported_versions.ts`	Introduced script for updating version references in documentation and configuration files.
`autoload/health/denops.vim`	Replaced hardcoded version constants with dynamic loading from JSON, enhancing version checks.
`deno.jsonc`	Added new task for applying supported versions.
`denops/supported_versions.json`	New file detailing supported versions for Deno, Vim, and Neovim.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub Actions
    participant Script
    participant JSON
    participant Vim

    User->>GitHub Actions: Trigger CI
    GitHub Actions->>JSON: Load supported versions
    GitHub Actions->>Script: Run version update
    Script->>JSON: Read version info
    Script->>Documentation: Update docs
    Script->>Vim: Update Vim configuration
    GitHub Actions-->>User: CI completed

Poem

In a world of code, both neat and bright,
A rabbit hops to fix with delight. 🐇
Versions updated, no more despair,
With tasks and scripts, we’ll take great care.
Hooray for the changes, let’s dance and sing,
For every new version, joy is the thing! 🎉✨

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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.` - `@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 as 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. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

codecov[bot] commented 1 month ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.52%. Comparing base (0608102) to head (de48a62).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #396 +/- ## ======================================= Coverage 95.52% 95.52% ======================================= Files 23 23 Lines 1384 1384 Branches 174 174 ======================================= Hits 1322 1322 Misses 59 59 Partials 3 3 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

vim-denops / denops.vim