Conversation
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
WalkthroughRemoves multiple changeset entries and pre-release config, updates root and package versions from release candidates to stable, and adds/updates changelogs across apps and packages, including introducing a new build-config changelog. No source code or public API changes are included. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 9
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (8)
packages/build-config/CHANGELOG.md (1)
1-4: Add a user-facing summary for 1.0.1.Entry is empty. Include a concise note on what changed (e.g., “Add changelog and bump version to align monorepo release; no functional changes.”).
Example:
## 1.0.1 - 2025-09-22 - Add package changelog and align version with monorepo release. No runtime changes.apps/extension/package.json (3)
242-244: Pin dependency instead of using wildcard."task-master-ai": "*" risks non‑reproducible builds. Pin to the released 0.27.0.
- "task-master-ai": "*" + "task-master-ai": "^0.27.0"
9-11: Align VS Code engine with @types/vscode to avoid runtime API drift.Types target 1.101.0 but engines declare ^1.93.0. Either raise engine or lower types to match.
# Option A: target latest runtime you develop against - "engines": { "vscode": "^1.93.0" }, + "engines": { "vscode": "^1.101.0" }, # Option B: keep engine, match types - "@types/vscode": "^1.101.0", + "@types/vscode": "^1.93.0",Also applies to: 261-261
227-241: CI safeguard: add a no‑uncommitted‑dist check to prevent publishing stale builds.Consider a "prepublishOnly" script that builds and verifies dist freshness before vsce packaging.
- "vscode:prepublish": "npm run build", + "vscode:prepublish": "npm run build", + "prepublishOnly": "git diff --quiet -- dist || (echo 'dist has uncommitted changes; run build' && exit 1)"CHANGELOG.md (4)
87-91: Typo: “udpate-task” → “update-task”.- Added automatic codebase analysis for Gemini CLI provider in parse-prd, and analyze-complexity, add-task, udpate-task, update, update-subtask commands + Added automatic codebase analysis for Gemini CLI provider in parse-prd, and analyze-complexity, add-task, update-task, update, update-subtask commands
762-763: Typos: “claude clode” and duplicate “of”.- - Provide claude clode with a complete set of of commands that can trigger task master events directly within Claude Code + - Provide Claude Code with a complete set of commands that can trigger Task Master events directly within Claude Code
1471-1471: Typo: “applicatoin” → “application”.- - No longer automatically creates individual task files as they are not used by the applicatoin. You can still generate them anytime using the `generate` command. + - No longer automatically creates individual task files as they are not used by the application. You can still generate them anytime using the `generate` command.
1845-1845: Typo: “Sonney” → “Sonnet”.- - Adjusts default main model model to Claude Sonnet 4. Adjusts default fallback to Claude Sonney 3.7" + - Adjusts default main model model to Claude Sonnet 4. Adjusts default fallback to Claude Sonnet 3.7"
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (23)
.changeset/clever-spies-obey.md(0 hunks).changeset/dry-dogs-rule.md(0 hunks).changeset/giant-clouds-remain.md(0 hunks).changeset/pre.json(0 hunks).changeset/pretty-planes-cross.md(0 hunks).changeset/ready-plums-worry.md(0 hunks).changeset/shiny-regions-teach.md(0 hunks).changeset/shy-tips-brake.md(0 hunks).changeset/smart-foxes-sit.md(0 hunks).changeset/weak-toes-clap.md(0 hunks).changeset/wild-ears-look.md(0 hunks)CHANGELOG.md(1 hunks)apps/cli/CHANGELOG.md(1 hunks)apps/cli/package.json(1 hunks)apps/docs/CHANGELOG.md(1 hunks)apps/docs/package.json(1 hunks)apps/extension/CHANGELOG.md(1 hunks)apps/extension/package.json(1 hunks)package.json(1 hunks)packages/build-config/CHANGELOG.md(1 hunks)packages/build-config/package.json(1 hunks)packages/tm-core/CHANGELOG.md(7 hunks)packages/tm-core/package.json(1 hunks)
💤 Files with no reviewable changes (11)
- .changeset/wild-ears-look.md
- .changeset/ready-plums-worry.md
- .changeset/weak-toes-clap.md
- .changeset/giant-clouds-remain.md
- .changeset/shy-tips-brake.md
- .changeset/pre.json
- .changeset/dry-dogs-rule.md
- .changeset/shiny-regions-teach.md
- .changeset/pretty-planes-cross.md
- .changeset/clever-spies-obey.md
- .changeset/smart-foxes-sit.md
🧰 Additional context used
📓 Path-based instructions (1)
package.json
📄 CodeRabbit inference engine (.cursor/rules/test_workflow.mdc)
Add and update test scripts in package.json to include test, test:watch, test:coverage, test:unit, test:integration, test:e2e, and test:ci
Files:
package.json
🧠 Learnings (10)
📓 Common learnings
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/new_features.mdc:0-0
Timestamp: 2025-07-18T17:12:57.903Z
Learning: Applies to .changeset/* : Create appropriate changesets for new features, use semantic versioning, include tagged system information in release notes, and document breaking changes if any.
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1178
File: packages/tm-core/src/auth/config.ts:5-7
Timestamp: 2025-09-02T21:51:27.921Z
Learning: The user Crunchyman-ralph prefers not to use node: scheme imports (e.g., 'node:os', 'node:path') for Node.js core modules and considers suggestions to change bare imports to node: scheme as too nitpicky.
📚 Learning: 2025-09-03T12:15:03.208Z
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1178
File: apps/cli/src/commands/auth.command.ts:222-224
Timestamp: 2025-09-03T12:15:03.208Z
Learning: The CLI can be invoked using both "task-master" and "tm" as aliases - both forms are valid and acceptable in help text, documentation, and examples.
Applied to files:
apps/cli/package.json
📚 Learning: 2025-07-18T17:10:12.881Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/dev_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:12.881Z
Learning: For CLI usage, install Taskmaster globally with `npm install -g task-master-ai` or use locally via `npx task-master-ai ...`.
Applied to files:
apps/cli/package.jsonpackage.jsonCHANGELOG.md
📚 Learning: 2025-07-31T20:49:04.638Z
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#997
File: apps/extension/package.publish.json:2-8
Timestamp: 2025-07-31T20:49:04.638Z
Learning: In the eyaltoledano/claude-task-master repository, the VS Code extension uses a 3-file packaging system where package.json (with name "extension") is for development within the monorepo, while package.publish.json (with name "task-master-hamster") contains the clean manifest for VS Code marketplace publishing. The different names are intentional and serve distinct purposes in the build and publishing workflow.
Applied to files:
apps/extension/package.json
📚 Learning: 2025-07-18T17:07:53.100Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Applies to .changeset/*.md : When running `npm run changeset` or `npx changeset add`, provide a concise summary of the changes for the `CHANGELOG.md` in imperative mood, typically a single line, and not a detailed Git commit message.
Applied to files:
apps/docs/CHANGELOG.mdapps/cli/CHANGELOG.md
📚 Learning: 2025-09-22T16:42:10.070Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: public/assets/.windsurfrules:0-0
Timestamp: 2025-09-22T16:42:10.070Z
Learning: Use the task-master CLI as the primary interface instead of node scripts/dev.js; install globally with npm -g or use npx; all commands accept the same options and include additional commands like init
Applied to files:
package.json
📚 Learning: 2025-07-18T17:07:53.100Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Applies to .changeset/*.md : The changeset summary should be user-facing, describing what changed in the released version that is relevant to users or consumers of the package.
Applied to files:
packages/build-config/CHANGELOG.md
📚 Learning: 2025-09-17T19:09:08.882Z
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1211
File: jest.resolver.cjs:8-15
Timestamp: 2025-09-17T19:09:08.882Z
Learning: In the eyaltoledano/claude-task-master project, the team only uses .ts files and does not plan to use .tsx or .mts extensions, so Jest resolver and build tooling should focus on .js → .ts mapping only.
Applied to files:
packages/tm-core/CHANGELOG.md
📚 Learning: 2025-07-18T17:10:53.657Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Guidelines for integrating new features into the Task Master CLI with tagged system considerations (new_features.mdc).
Applied to files:
CHANGELOG.md
📚 Learning: 2025-08-11T12:30:23.843Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: CLAUDE.md:0-0
Timestamp: 2025-08-11T12:30:23.843Z
Learning: Import Task Master's development workflow commands and guidelines; treat the contents of ./.taskmaster/CLAUDE.md as if included in the main CLAUDE.md
Applied to files:
CHANGELOG.md
🪛 markdownlint-cli2 (0.18.1)
CHANGELOG.md
19-19: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
22-22: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
24-24: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
26-26: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
34-34: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
40-40: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Test
🔇 Additional comments (2)
apps/cli/CHANGELOG.md (1)
3-9: LGTM — changelog clearly reflects dependency bump.Entry is sufficient for 0.27.0.
package.json (1)
3-3: LGTM for root package.json (version 0.27.0); repo-wide verification inconclusive.
Root package.json looks fine. Sandbox runs produced no output — run the included repo-wide check locally and paste its output to confirm required test scripts exist in every package.json.
| { | ||
| "name": "@tm/cli", | ||
| "version": "0.27.0-rc.0", | ||
| "version": "0.27.0", |
There was a problem hiding this comment.
🧩 Analysis chain
LGTM — scripts meet the repo test requirements.
Version bump and script set look good.
If helpful, verify e2e folder exists to prevent script failures:
🏁 Script executed:
#!/bin/bash
fd -a 'package.json' apps/cli -x bash -lc 'jq -r .scripts["test:e2e"] {} && test -d apps/cli/tests/e2e && echo "e2e dir OK" || echo "e2e dir missing"'Length of output: 309
Fix required — e2e tests missing & verification command failing
Verification output shows "e2e dir missing" plus jq compile errors. Ensure apps/cli/tests/e2e exists or update apps/cli/package.json's "test:e2e" script (file: apps/cli/package.json), and fix the verification command quoting.
- Action: add apps/cli/tests/e2e or change the test:e2e script so CI won't fail.
- Quick local checks (run from repo root):
jq -r '.scripts["test:e2e"]' apps/cli/package.json 2>/dev/null || echo "no test:e2e script"
[ -d apps/cli/tests/e2e ] && echo "e2e dir OK" || echo "e2e dir missing"
🤖 Prompt for AI Agents
In apps/cli/package.json around line 3, the CI is failing because the repo
either lacks apps/cli/tests/e2e or the "test:e2e" npm script is incorrect/poorly
quoted causing jq compile errors; fix by either adding the missing tests
directory apps/cli/tests/e2e with appropriate e2e tests, or update the
"test:e2e" script in apps/cli/package.json to a valid command (e.g., a no-op or
real test runner) and ensure the verification command uses proper
quoting/escaping so jq can parse the script value (adjust single/double quotes
or escape characters as needed) so the local checks and CI both report the e2e
dir or valid script.
| @@ -1,5 +1,7 @@ | |||
| # docs | |||
|
|
|||
| ## 0.0.3 | |||
There was a problem hiding this comment.
🧹 Nitpick
Add a brief, user-facing note for 0.0.3.
Provide a one-liner describing what changed (e.g., “Bump docs package version; no content changes.”).
Example:
## 0.0.3 - 2025-09-22
- Version bump to align with monorepo release; no docs content changes.
🤖 Prompt for AI Agents
In apps/docs/CHANGELOG.md around line 3, the 0.0.3 entry lacks a user-facing
note; add a single-line changelog entry under "## 0.0.3" summarizing the change
(include date if desired), for example a brief one-liner like "0.0.3 -
YYYY-MM-DD: Version bump to align with monorepo release; no docs content
changes." to clearly communicate the release intent.
| { | ||
| "name": "docs", | ||
| "version": "0.0.2", | ||
| "version": "0.0.3", |
There was a problem hiding this comment.
Add required test scripts per repo guidelines.
This package.json lacks the mandated test scripts (test, test:watch, test:coverage, test:unit, test:integration, test:e2e, test:ci). For docs (Mintlify) where tests aren’t applicable, add no-op placeholders to satisfy tooling.
Suggested scripts block to add:
{
"scripts": {
"dev": "mintlify dev",
"preview": "mintlify preview",
"test": "node -e 'process.exit(0)'",
"test:watch": "node -e 'process.exit(0)'",
"test:coverage": "node -e 'process.exit(0)'",
"test:unit": "node -e 'process.exit(0)'",
"test:integration": "node -e 'process.exit(0)'",
"test:e2e": "node -e 'process.exit(0)'",
"test:ci": "node -e 'process.exit(0)'"
}
}🤖 Prompt for AI Agents
In apps/docs/package.json around line 3, the package is missing the mandated
test scripts required by repo tooling; add a "scripts" section (or extend the
existing one) to include the dev and preview entries plus no-op placeholders for
test, test:watch, test:coverage, test:unit, test:integration, test:e2e, and
test:ci that simply exit successfully (e.g., using a node -e 'process.exit(0)'
command) so tooling recognizes tests without changing Mintlify behavior; ensure
valid JSON structure and do not duplicate existing script keys.
| ## 0.25.0 | ||
|
|
||
| ### Minor Changes | ||
|
|
||
| - [#1200](https://github.com/eyaltoledano/claude-task-master/pull/1200) [`fce8414`](https://github.com/eyaltoledano/claude-task-master/commit/fce841490a9ebbf1801a42dd8a29397379cf1142) Thanks [@eyaltoledano](https://github.com/eyaltoledano)! - Add "Start Task" button to VS Code extension for seamless Claude Code integration | ||
|
|
||
| You can now click a "Start Task" button directly in the Task Master extension which will open a new terminal and automatically execute the task using Claude Code. This provides a seamless workflow from viewing tasks in the extension to implementing them without leaving VS Code. | ||
|
|
||
| - [#1201](https://github.com/eyaltoledano/claude-task-master/pull/1201) [`83af314`](https://github.com/eyaltoledano/claude-task-master/commit/83af314879fc0e563581161c60d2bd089899313e) Thanks [@losolosol](https://github.com/losolosol)! - Added a Start Build button to the VSCODE Task Properties Right Panel | ||
|
|
||
| ### Patch Changes | ||
|
|
||
| - [#1229](https://github.com/eyaltoledano/claude-task-master/pull/1229) [`674d1f6`](https://github.com/eyaltoledano/claude-task-master/commit/674d1f6de7ea98116b61bdae6198bafe6c4e7c1a) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix MCP not connecting to new Taskmaster version | ||
|
|
||
| - Updated dependencies [[`4e12643`](https://github.com/eyaltoledano/claude-task-master/commit/4e126430a092fb54afb035514fb3d46115714f97), [`fce8414`](https://github.com/eyaltoledano/claude-task-master/commit/fce841490a9ebbf1801a42dd8a29397379cf1142), [`fce8414`](https://github.com/eyaltoledano/claude-task-master/commit/fce841490a9ebbf1801a42dd8a29397379cf1142), [`fce8414`](https://github.com/eyaltoledano/claude-task-master/commit/fce841490a9ebbf1801a42dd8a29397379cf1142), [`a621ff0`](https://github.com/eyaltoledano/claude-task-master/commit/a621ff05eafb51a147a9aabd7b37ddc0e45b0869), [`e6de285`](https://github.com/eyaltoledano/claude-task-master/commit/e6de285ceacb0a397e952a63435cd32a9c731515), [`fce8414`](https://github.com/eyaltoledano/claude-task-master/commit/fce841490a9ebbf1801a42dd8a29397379cf1142)]: | ||
| - task-master-ai@0.27.0 | ||
|
|
There was a problem hiding this comment.
🧹 Nitpick
Changelog entry matches manifest; add release date for 0.25.0.
Add a date per Keep a Changelog, e.g., “## 0.25.0 – 2025-09-22”.
🤖 Prompt for AI Agents
In apps/extension/CHANGELOG.md around lines 3 to 19, the "## 0.25.0" release
header lacks a release date; update the heading to include the date per Keep a
Changelog, e.g. change "## 0.25.0" to "## 0.25.0 – 2025-09-22".
| "displayName": "TaskMaster", | ||
| "description": "A visual Kanban board interface for TaskMaster projects in VS Code", | ||
| "version": "0.25.0-rc.0", | ||
| "version": "0.25.0", |
There was a problem hiding this comment.
🧩 Analysis chain
Version bump looks good; confirm publish manifest too.
Version to 0.25.0 matches CHANGELOG. Please also bump apps/extension/package.publish.json to 0.25.0 so Marketplace packaging stays in sync.
🏁 Script executed:
#!/bin/bash
# Verify publish manifest version alignment
fd -a 'package.publish.json' apps/extension | xargs -I{} jq -r '.version' {} || echo "package.publish.json not found"Length of output: 6
Bump apps/extension/package.publish.json to 0.25.0
apps/extension/package.json is 0.25.0 but apps/extension/package.publish.json is still 0.23.1 (verified); update apps/extension/package.publish.json to 0.25.0 so Marketplace packaging stays in sync.
🤖 Prompt for AI Agents
In apps/extension/package.publish.json (the "version" field) update the version
to match apps/extension/package.json by changing the current 0.23.1 value to
0.25.0 so Marketplace packaging stays in sync.
| ## Setup Instructions | ||
| 1. **Get your Grok API key** from [console.x.ai](https://console.x.ai) | ||
| 2. **Set the environment variable**: | ||
| ```bash | ||
| export GROK_CLI_API_KEY="your-api-key-here" | ||
| ``` | ||
| 3. **Configure Task Master to use Grok**: | ||
| ```bash | ||
| task-master models --set-main grok-beta | ||
| # or | ||
| task-master models --set-research grok-beta | ||
| # or | ||
| task-master models --set-fallback grok-beta | ||
| ``` | ||
|
|
||
| ## Key Features | ||
| - **Full codebase context**: Grok models can analyze your entire project when generating tasks or parsing PRDs | ||
| - **xAI model access**: Support for latest Grok models (grok-2, grok-3, grok-4, etc.) | ||
| - **Code-aware task generation**: Create more accurate and contextual tasks based on your actual codebase | ||
| - **Intelligent PRD parsing**: Parse requirements with understanding of your existing code structure | ||
|
|
||
| ## Available Models | ||
| - `grok-beta` - Latest Grok model with codebase context | ||
| - `grok-vision-beta` - Grok with vision capabilities and codebase context | ||
|
|
||
| The Grok CLI provider integrates with xAI's Grok models via grok-cli and can also use the local Grok CLI configuration file (`~/.grok/user-settings.json`) if available. | ||
|
|
||
| ## Credits | ||
|
|
There was a problem hiding this comment.
🧹 Nitpick
🧩 Analysis chain
Markdownlint: add blank lines around fenced code blocks.
Several fenced blocks (e.g., Setup Instructions) lack blank lines before/after, triggering MD031/MD022.
🏁 Script executed:
#!/bin/bash
# Run markdownlint on changed files and show offending lines
npx -y markdownlint-cli2 CHANGELOG.md | sed -n '1,120p'Length of output: 66809
Markdownlint: add blank lines around headings and fenced code blocks in CHANGELOG.md (lines 19–47).
markdownlint reports MD022 (headings not surrounded by blank lines) and MD031 (fenced code blocks not surrounded by blank lines) in this section — add a single blank line above and below the "## Setup Instructions" / "## Key Features" headings and immediately before and after each bash fenced block (MD022 at lines 19,34; MD031 at lines 22,24,26).
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
19-19: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
22-22: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
24-24: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
26-26: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
34-34: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
40-40: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
In CHANGELOG.md around lines 19 to 47, markdownlint flags missing blank lines
around headings and fenced code blocks; add a single blank line above and below
the "## Setup Instructions" and "## Key Features" headings, and ensure there is
one blank line immediately before and after each ```bash``` fenced block (the
three blocks in the Setup Instructions section) so that MD022 and MD031 are
resolved.
| { | ||
| "name": "@tm/build-config", | ||
| "version": "1.0.0", | ||
| "version": "1.0.1", |
There was a problem hiding this comment.
Add required test scripts per repo guidelines.
This package.json is missing the standard test scripts set. If this package has no tests, wire them as no-ops so CI remains consistent.
Suggested scripts to append (keep existing ones):
{
"scripts": {
"build": "tsc",
"typecheck": "tsc --noEmit",
"test": "node -e 'process.exit(0)'",
"test:watch": "node -e 'process.exit(0)'",
"test:coverage": "node -e 'process.exit(0)'",
"test:unit": "node -e 'process.exit(0)'",
"test:integration": "node -e 'process.exit(0)'",
"test:e2e": "node -e 'process.exit(0)'",
"test:ci": "node -e 'process.exit(0)'"
}
}🤖 Prompt for AI Agents
In packages/build-config/package.json around line 3, the package.json is missing
the standard test scripts required by repo guidelines; add the recommended
scripts section (preserving any existing scripts) that includes build and
typecheck plus the no-op test entries: test, test:watch, test:coverage,
test:unit, test:integration, test:e2e, and test:ci (each wired to a no-op like
`node -e 'process.exit(0)'`) so CI sees consistent script names while keeping
any current script entries intact.
| ## 0.26.1 | ||
|
|
There was a problem hiding this comment.
🧹 Nitpick
Place intro above first version header and include a date for 0.26.1.
Move the “All notable changes…” paragraph above “## 0.26.1” and add a release date for 0.26.1 to keep consistency.
🤖 Prompt for AI Agents
In packages/tm-core/CHANGELOG.md around lines 3 to 4, the opening descriptive
paragraph ("All notable changes...") should be moved above the first version
header and a release date must be added to the "## 0.26.1" header; edit the file
so the intro paragraph appears before the "## 0.26.1" heading and update that
heading to include the release date in YYYY-MM-DD format (e.g., "## 0.26.1 -
2025-09-22") to match the project changelog conventions.
| { | ||
| "name": "@tm/core", | ||
| "version": "0.26.0", | ||
| "version": "0.26.1", |
There was a problem hiding this comment.
Complete the standard test script matrix.
You have test, test:watch, and test:coverage. Add test:unit, test:integration, test:e2e, and test:ci for consistency across workspaces.
Suggested additions (Vitest-based):
{
"scripts": {
"test:unit": "vitest run -t unit",
"test:integration": "vitest run -t integration",
"test:e2e": "vitest run --dir tests/e2e",
"test:ci": "vitest run --coverage --reporter=dot"
}
}🤖 Prompt for AI Agents
In packages/tm-core/package.json around line 3, the project lacks the full
standardized test script matrix; add the missing Vitest-based npm scripts:
test:unit (vitest run -t unit), test:integration (vitest run -t integration),
test:e2e (vitest run --dir tests/e2e), and test:ci (vitest run --coverage
--reporter=dot) into the "scripts" section alongside the existing test,
test:watch, and test:coverage entries so workspaces are consistent (do not
modify the version field).
This PR was automatically generated to update documentation based on recent changes. Original commit: Merge pull request #1231 from eyaltoledano/ralph/merge.from.main\n\n\n Co-authored-by: Claude <claude-assistant@anthropic.com>
1 participant
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
What type of PR is this?
Description
Related Issues
How to Test This
# Example commands or stepsExpected result:
Contributor Checklist
npm run changesetnpm testnpm run format-check(ornpm run formatto fix)Changelog Entry
For Maintainers
Summary by CodeRabbit
New Features
Improvements
Bug Fixes
Documentation
Chores