build: Update yscope-dev-utils and unlock task version

[sitaowang1998]

Description

In #22, task version is locked to 3.39.2 temporarily as a workaround. Now the upstream yscope-dev-utils have updated and solved the problem, we can remove the task version lock.

Validation performed

• Github workflow succeeded.

Summary by CodeRabbit

• New Features

  • Updated the version requirement for the [Task] dependency in the README to allow for broader compatibility.

• Bug Fixes

  • Removed version locks for the task utility in the development container and code-linting workflow, enabling the installation of the latest version.

• Documentation

  • Revised the README to reflect the updated version constraint for the [Task] dependency.

[coderabbitai]

Walkthrough

The changes in this pull request involve modifications to the Dockerfile, workflow configuration for code linting, and the README file. The Dockerfile and workflow now install the latest version of the task utility by removing the previous version lock of 3.39.2. The README file has been updated to reflect a broader version requirement for the Task dependency, changing it from >= 3.38.0, < 3.40.0 to 3.38.0 or higher. No other structural changes were made to the files.

Changes

File	Change Summary
.devcontainer/Dockerfile	Removed version lock for task utility, allowing installation of the latest version.
.github/workflows/code-linting-checks.yaml	Updated installation command for @go-task/cli to remove version lock, allowing latest version.
README.md	Updated version requirement for [Task] from >= 3.38.0, < 3.40.0 to 3.38.0 or higher.
tools/yscope-dev-utils	Updated subproject commit reference from 159768c7d171595ed2cba17b758c10043a2efe96 to ad576e43c1a43d7a6afde79fc9c3c952b7bf28bd.

Possibly related PRs

• fix: Lock task to v3.39.2 to work around behaviour change in v3.40.0. #22: The changes in this PR involve locking the version of the task utility to v3.39.2 in the Dockerfile and workflow configuration, which directly relates to the version management of task in the main PR, where the version lock was removed.

Suggested reviewers

• kirkrodrigues

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between eec3532 and 1b05e2f.

📒 Files selected for processing (1)

• tools/yscope-dev-utils (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• tools/yscope-dev-utils

---

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.