chore: lint fix

[JounQin]

Summary by CodeRabbit

• Documentation
  • Adjusted heading anchors in the DevOps v3→v4 upgrade guide to improve consistency; anchor IDs now follow default generation.
• Chores
  • Updated package manager to Yarn 4.9.4 for improved tooling stability.
  • Bumped development dependency versions for maintenance.
  • Expanded spell-check dictionary to include industry terminology.

[coderabbitai]

Walkthrough

Introduces a cSpell compound dictionary file, updates Yarn from 4.9.2 to 4.9.4 in config and package.json, bumps @alauda/doom devDependency, and escapes explicit header anchors in an MDX upgrade doc.

Changes

Cohort / File(s)	Summary
Spelling config \.cspell/compound.txt	Added new cSpell compound dictionary file containing tektoncd.
Build/tooling versions .yarnrc.yml, package.json	Updated Yarn path/version from 4.9.2 to 4.9.4; bumped devDependency @alauda/doom from ^1.10.10 to ^1.12.1. No runtime logic changes.
Docs (MDX anchors) docs/en/upgrade/upgrading-devops-v3-to-v4.mdx	Escaped {#...} in three headings to \{#...}, changing how header IDs/anchors are generated. No other content changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• docs:upgrading Alauda DevOps from ACP 3.18 to 4.x. #59 — Also modifies the same MDX headings’ anchor syntax.
• chore: add v3 plugin release notes #47 — Edits the same upgrade doc (renames operators and updates compatibility matrix).
• feat: enable and fix doom lint issues #38 — Touches spelling config and tooling (cSpell, Yarn, and @alauda/doom) similar to this PR.

Suggested reviewers

• danielfbm
• kycheng
• yhuan123

Poem

A nibble of yarn, a hop through docs,
I tweak the anchors, adjust the locks.
Doom steps up, spells align—
Tektoncd now looks just fine.
Thump-thump! My review burrow’s clear,
Small hops forward, changes near. 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 239f718 and ec1a2cd.

⛔ Files ignored due to path filters (2)

• .yarn/releases/yarn-4.9.4.cjs is excluded by !**/.yarn/**
• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (4)

• .cspell/compound.txt (1 hunks)
• .yarnrc.yml (1 hunks)
• docs/en/upgrade/upgrading-devops-v3-to-v4.mdx (3 hunks)
• package.json (2 hunks)

🔇 Additional comments (7)

.cspell/compound.txt (1)

1-1: LGTM! Good addition to the spell-check dictionary.

Adding "tektoncd" to the compound words dictionary will prevent false spelling errors for this legitimate term used in the DevOps documentation.

package.json (2)

3-3: LGTM! DevDependency version bump looks good.

The update from ^1.10.10 to ^1.12.1 for @alauda/doom appears to be a reasonable minor version bump that should include bug fixes and improvements.

---

13-13: LGTM! Package manager version is consistent with .yarnrc.yml.

The yarn version bump to 4.9.4 aligns with the corresponding update in .yarnrc.yml, maintaining consistency across the project configuration.

.yarnrc.yml (1)

7-7: LGTM! Yarn path update is consistent with package.json.

The yarn path update to yarn-4.9.4.cjs correctly aligns with the packageManager version specified in package.json, ensuring consistent tooling across the project.

docs/en/upgrade/upgrading-devops-v3-to-v4.mdx (3)

10-10: LGTM! Proper MDX header anchor escaping.

Escaping the explicit anchor {#Version} with a backslash prevents MDX parsing issues while maintaining the intended heading structure.

---

51-51: LGTM! Consistent anchor escaping applied.

The escaping of {#Migration} maintains consistency with the other header anchor fixes in this file.

---

61-61: LGTM! Final anchor escaping completes the fix.

The escaping of {#UI} completes the consistent application of the MDX header anchor fix throughout the document.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/lint

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbit in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbit 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:
  • @coderabbit gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbit read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbit help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbit ignore or @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbit summary or @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbit or @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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.