chore: remove stale TODO comment

[cherkanovart]

Summary

• Remove empty // TODO comment from typescript loader spec
• Includes a changeset to trigger a release (unblocks publish of pending 0.133.10 changes)

Test plan

• CI passes
• After merge, release workflow creates a release PR bumping to 0.133.11

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Removed stale TODO comment from the CLI test suite to improve code organization and reduce technical debt.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 30caa9c4-1690-4dd2-af4a-0ace7005ca37

📥 Commits

Reviewing files that changed from the base of the PR and between adc1f42 and 58ced2f.

📒 Files selected for processing (2)

• .changeset/remove-stale-todo.md
• packages/cli/src/cli/loaders/typescript/index.spec.ts

💤 Files with no reviewable changes (1)

• packages/cli/src/cli/loaders/typescript/index.spec.ts

---

📝 Walkthrough

Walkthrough

Removes a stale TODO comment from a TypeScript test file and documents the cleanup via a new Changeset entry marking a patch version bump for the lingo.dev package.

Changes

Cohort / File(s)	Summary
Stale TODO Removal .changeset/remove-stale-todo.md, packages/cli/src/cli/loaders/typescript/index.spec.ts	Deletes a dangling TODO comment from the test file and creates a Changeset documentation file to track the patch-level cleanup as a release note.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• vrcprl
• AndreyHirsa

Poem

🐰 A TODO long forgotten, now set free,
Comment deleted with grace, cleanup decree,
Changeset marked, the ledger is clear,
One less distraction cluttering here! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description covers the main change and rationale but lacks required sections (Changes list, Testing with checkboxes, Visuals, and full Checklist as per template).	Add a 'Changes' section with bullet points, complete the 'Testing' section with proper checkboxes and pass status, and ensure all Checklist items are properly addressed with checkboxes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and directly summarizes the main change: removing a stale TODO comment, which is the primary focus of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/remove-empty-changeset

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}