chore: Update to latest yscope-dev-utils.

[davidlion]

Description

Update the yscope-dev-utils submodule to the latest version. This includes a breaking change to compute-checksum and validate-checksum. This PR updates the arguments to these tasks to use the new version.

Checklist

• The PR satisfies the contribution guidelines.
• This is a breaking change and that has been indicated in the PR title, OR this isn't a
  breaking change.
• Necessary docs have been updated, OR no docs need to be updated.

Validation performed

Ran the default task twice to confirm completed tasks are correctly skipped.

Summary by CodeRabbit

• Chores
  • Standardized variable usage for checksum validation and directory management across multiple tasks, enhancing clarity and consistency.
  • Updated dependency references for development utilities to ensure reliable, up-to-date support.

This update includes improvements that enhance consistency and maintainability throughout our build operations.

[coderabbitai]

Walkthrough

The pull request standardizes variable usage across multiple task definitions by replacing DATA_DIR with INCLUDE_PATTERNS (an array format) and OUTPUT_FILE with CHECKSUM_FILE in various checksum-related tasks. Changes are applied in several configuration files for tasks in packaging, dependency processing, documentation, and linting. Additionally, a subproject commit hash in the tools/yscope-dev-utils directory was updated.

Changes

File(s)	Change Summary
Taskfile.yml	Replaced DATA_DIR with INCLUDE_PATTERNS (as an array with the output directory path) and updated OUTPUT_FILE to CHECKSUM_FILE in the utils:validate-checksum and utils:compute-checksum tasks (affecting tasks like package, webui, etc.).
deps-tasks.yml	Updated variable usage in checksum validation tasks by substituting DATA_DIR with INCLUDE_PATTERNS (array containing destination directories) and removed OUTPUT_FILE in the compute-checksum commands across multiple dependency tasks (e.g., abseil-cpp, antlr4).
docs/tasks.yml	Modified checksum-related declarations by replacing DATA_DIR with INCLUDE_PATTERNS (referencing OUTPUT_DIR in an array) and substituting OUTPUT_FILE with CHECKSUM_FILE in tasks such as site, docs-venv, and http-server.
lint-tasks.yml	In the linter-node-modules and venv tasks, replaced DATA_DIR with INCLUDE_PATTERNS (array with OUTPUT_DIR) and adjusted the checksum command to use CHECKSUM_FILE instead of OUTPUT_FILE.
tools/yscope-dev-utils	Updated the subproject commit hash from c1593f7414112f2b6e0bf46595126c8edeffe106 to c8b5d5c26506a1db8d5ec0f183f4e5fa7417fb66.

Suggested reviewers

• kirkrodrigues

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 77bfbbe and 8fb9903.

📒 Files selected for processing (3)

• Taskfile.yml (16 hunks)
• docs/tasks.yml (5 hunks)
• lint-tasks.yml (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• lint-tasks.yml

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: build-macos (macos-14, false)
• GitHub Check: build-macos (macos-13, false)
• GitHub Check: build-macos (macos-13, true)
• GitHub Check: lint-check (ubuntu-latest)
• GitHub Check: lint-check (macos-latest)

🔇 Additional comments (14)

docs/tasks.yml (5)

31-31: Standardised INCLUDE_PATTERNS in the site task dependency.
The new INCLUDE_PATTERNS: ["{{.OUTPUT_DIR}}"] correctly replaces the old DATA_DIR usage for checksum validation. This change aligns with the update objectives.

---

52-53: Consistent update for compute-checksum in the site task.
The inclusion of INCLUDE_PATTERNS along with the existing CHECKSUM_FILE maintains consistency with the new argument requirements for checksum tasks.

---

67-67: Updated REQUIREMENTS_FILE path in docs-venv.
The new value {{.ROOT_DIR}}/docs/requirements.txt ensures that the requirements file is resolved relative to the project root. Please verify that this file exists at the specified location.

---

73-73: Standardised INCLUDE_PATTERNS in the docs-venv task.
By adding INCLUDE_PATTERNS: ["{{.OUTPUT_DIR}}"] in the dependency on :utils:validate-checksum, the variable usage is now consistent with the new approach for checksum operations.

---

101-101: Consistent variable update in the http-server task.
The addition of INCLUDE_PATTERNS: ["{{.OUTPUT_DIR}}"] in the :utils:validate-checksum dependency ensures that the http-server task also adheres to the updated checksum parameter conventions.

Taskfile.yml (9)

7-7: Updated utils submodule reference in includes.
The change from the old filename to "tools/yscope-dev-utils/taskfiles/utils.yaml" ensures that the Taskfile now correctly includes the updated utils file.

---

30-30: Aligned G_UTILS_TASKFILE variable with the new utils path.
The variable G_UTILS_TASKFILE now correctly points to the new utils.yaml file, matching the updated submodule.

---

117-119: Standardised INCLUDE_PATTERNS in the package task.
Adding INCLUDE_PATTERNS: ["{{.OUTPUT_DIR}}"] to the utils:validate-checksum dependency improves clarity over which directories are scanned during checksum computation.

---

551-553: Consistent INCLUDE_PATTERNS update in package-venv.
The addition of INCLUDE_PATTERNS: ["{{.OUTPUT_DIR}}"] in the package-venv task’s dependency on utils:validate-checksum ensures the task adheres to the new argument format.

---

559-559: Updated REQUIREMENTS_FILE in package-venv’s create-venv command.
The updated REQUIREMENTS_FILE: "{{.ROOT_DIR}}/requirements.txt" now directly references the correct file path from the project root. Confirm that this change is intentional and that the file is available.

---

562-565: Standardised compute-checksum in package-venv.
By setting both CHECKSUM_FILE and INCLUDE_PATTERNS in the compute-checksum task, the configuration now matches the updated standard seen across other tasks.

---

615-617: Updated INCLUDE_PATTERNS in webui-node-modules.
The change to include INCLUDE_PATTERNS: ["{{.OUTPUT_DIR}}"] in the validate-checksum dependency ensures that the webui node modules are correctly processed under the new checksum schema.

---

645-646: Component-venv checksum validation update.
Adding INCLUDE_PATTERNS: ["{{.OUTPUT_DIR}}"] in the dependency on utils:validate-checksum standardises the approach for component virtual environments. Confirm that the output directory is correctly set for these components.

---

654-657: Consistent compute-checksum update in component-venv.
The compute-checksum task has been updated to include both CHECKSUM_FILE and INCLUDE_PATTERNS, reflecting the uniform updates made throughout the Taskfile.

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[kirkrodrigues]

Can you resolve the workflow failure?