@mastra/factory 0.28.0-alpha.10 → 0.28.0-alpha.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -0
- package/dist/capabilities/version-control.d.ts +6 -1
- package/dist/capabilities/version-control.d.ts.map +1 -1
- package/dist/environment/build-schedule.js +1 -1
- package/dist/environment/build-schedule.js.map +1 -1
- package/dist/environment/build.d.ts +3 -3
- package/dist/environment/build.d.ts.map +1 -1
- package/dist/environment/build.js +3 -1
- package/dist/environment/build.js.map +1 -1
- package/dist/environment/heads.d.ts +1 -1
- package/dist/environment/heads.d.ts.map +1 -1
- package/dist/environment/heads.js +4 -1
- package/dist/environment/heads.js.map +1 -1
- package/dist/environment/repository-access.d.ts +13 -0
- package/dist/environment/repository-access.d.ts.map +1 -0
- package/dist/environment/repository-access.js +55 -0
- package/dist/environment/repository-access.js.map +1 -0
- package/dist/integrations/platform/github/integration.d.ts.map +1 -1
- package/dist/integrations/platform/github/integration.js +18 -12
- package/dist/integrations/platform/github/integration.js.map +1 -1
- package/dist/integrations/slack/integration.d.ts.map +1 -1
- package/dist/integrations/slack/integration.js +7 -4
- package/dist/integrations/slack/integration.js.map +1 -1
- package/dist/routes/board-snapshot.d.ts +6 -0
- package/dist/routes/board-snapshot.d.ts.map +1 -1
- package/dist/routes/board-snapshot.js +23 -6
- package/dist/routes/board-snapshot.js.map +1 -1
- package/dist/routes/contracts.d.ts +6 -0
- package/dist/routes/contracts.d.ts.map +1 -1
- package/dist/routes/contracts.js +11 -0
- package/dist/routes/contracts.js.map +1 -1
- package/dist/routes/work-items.d.ts.map +1 -1
- package/dist/routes/work-items.js +60 -6
- package/dist/routes/work-items.js.map +1 -1
- package/dist/session/live-sessions.d.ts +1 -1
- package/dist/session/live-sessions.d.ts.map +1 -1
- package/dist/session/live-sessions.js +12 -2
- package/dist/session/live-sessions.js.map +1 -1
- package/dist/storage/domains/work-items/base.d.ts.map +1 -1
- package/dist/storage/domains/work-items/base.js +15 -2
- package/dist/storage/domains/work-items/base.js.map +1 -1
- package/dist/storage/domains/work-items/cards.d.ts.map +1 -1
- package/dist/storage/domains/work-items/cards.js +1 -1
- package/dist/storage/domains/work-items/cards.js.map +1 -1
- package/dist/work-items/related-cards.d.ts +21 -0
- package/dist/work-items/related-cards.d.ts.map +1 -0
- package/dist/work-items/related-cards.js +45 -0
- package/dist/work-items/related-cards.js.map +1 -0
- package/dist/workspace.d.ts.map +1 -1
- package/dist/workspace.js +7 -14
- package/dist/workspace.js.map +1 -1
- package/factory-skills/factory-build/SKILL.md +1 -1
- package/factory-skills/factory-self-review/SKILL.md +1 -1
- package/package.json +8 -8
|
@@ -53,7 +53,7 @@ Move the card with `factory_transition_work_item`, using the `expectedRevision`
|
|
|
53
53
|
|
|
54
54
|
Pick the path from the moves the signal's `Next phases` line allows out of this phase. A change request of this session that is already open decides first (the last bullet); the others apply only when none is open:
|
|
55
55
|
|
|
56
|
-
- **Open the change request** (the usual path, and the only one on the default Work board, which has no self-review phase; it needs the `pull request review` phase in `Next phases`, and a board whose `Board phases by part:` names no `self-review` phase): open the change request from the pushed head with `source_control_create_change_request` (head: the work branch; base: the default branch). Title it after the work item, summarize the change and its verification in the body, and link the source issue (`Fixes #<n>` on GitHub, `Closes #<n>` on GitLab). Then move the card to its `pull request review` phase (`pr-review`, named Review, on the default board). That phase takes the card only once Factory has attached the change request to it, which happens when the provider reports it opened. If the move is refused because the card has no pull request yet, wait briefly (`sleep 20`), re-read the revision from the latest `factory-phase` signal, and retry, up to three times; if it is still refused, the change request is tracked on its own card instead (a manual card, or an issue from another provider than the repository): the project's intake routes decide where that card goes. Post the change request link, say it is tracked on its own card and that a person should confirm it is reviewed there, and leave this card where it is.
|
|
56
|
+
- **Open the change request** (the usual path, and the only one on the default Work board, which has no self-review phase; it needs the `pull request review` phase in `Next phases`, and a board whose `Board phases by part:` names no `self-review` phase): open the change request from the pushed head with `source_control_create_change_request` (head: the work branch; base: the default branch). Title it after the work item, summarize the change and its verification in the body, and link the source issue (`Fixes #<n>` on GitHub, `Closes #<n>` on GitLab, `Fixes <ID>` such as `Fixes ENG-123` for a Linear issue; one line per issue when the card has several; for an issue the work only partly resolves, use `Refs #<n>` or `Ref <ID>` instead so the merge does not close it). Then move the card to its `pull request review` phase (`pr-review`, named Review, on the default board). That phase takes the card only once Factory has attached the change request to it, which happens when the provider reports it opened. If the move is refused because the card has no pull request yet, wait briefly (`sleep 20`), re-read the revision from the latest `factory-phase` signal, and retry, up to three times; if it is still refused, the change request is tracked on its own card instead (a manual card, or an issue from another provider than the repository): the project's intake routes decide where that card goes. Post the change request link, say it is tracked on its own card and that a person should confirm it is reviewed there, and leave this card where it is.
|
|
57
57
|
- **The board has a self-review phase** (`Board phases by part:` names a `self-review` phase and it is in `Next phases`): this path comes before opening the change request, even when the `pull request review` phase is in `Next phases` too, because Factory refuses a change request on a board with a self-review phase until self-review approves. Do not open a pull or merge request. Move the card to its `self-review` phase. An independent reviewer tests the branch there and opens the change request once it approves.
|
|
58
58
|
- **The board has a self-review phase that is not in `Next phases`:** open no change request (Factory refuses it until self-review approves) and move nothing. Ask the person with `ask_user` to let this phase move to the self-review phase, naming the pushed head, and wait for their answer.
|
|
59
59
|
- **Neither review phase is in `Next phases`:** open no change request and move nothing. Ask the person with `ask_user` which move this board should allow out of this phase, naming the pushed head, and wait for their answer.
|
|
@@ -59,7 +59,7 @@ On request changes, post the report as your final conversation message and stop.
|
|
|
59
59
|
On approve, keep the card where it is until the change request exists:
|
|
60
60
|
|
|
61
61
|
1. Confirm `origin/<branch>` still points at the head you approved (`git ls-remote origin <branch>`). If it moved, do not open anything: record a fresh review of the new head instead.
|
|
62
|
-
2. Open the change request from that head with `source_control_create_change_request` (head: the work branch; base: the default branch). Title it after the work item; put your report in the body and link the source issue (`Fixes #<n>` on GitHub, `Closes #<n>` on GitLab) when the card has one. Factory refuses a change request whose head is not the approved one.
|
|
62
|
+
2. Open the change request from that head with `source_control_create_change_request` (head: the work branch; base: the default branch). Title it after the work item; put your report in the body and link the source issue (`Fixes #<n>` on GitHub, `Closes #<n>` on GitLab, `Fixes <ID>` such as `Fixes ENG-123` for a Linear issue; one line per issue when the card has several; for an issue the work only partly resolves, use `Refs #<n>` or `Ref <ID>` instead so the merge does not close it) when the card has one. Factory refuses a change request whose head is not the approved one.
|
|
63
63
|
3. On GitHub, Factory moves the card to pull request review itself when the pull request opens from the head you approved: if the latest `factory-phase` signal shows the card already there, skip this step. Otherwise move the card to the `pull request review` phase the `factory-phase` signal's `Board phases by part:` line names (`pr-review` on the default board) with `factory_transition_work_item` (`expectedRevision` from the latest `factory-phase` signal), with a one-sentence rationale naming the change request. Opening the change request can move the card's revision on under you (attaching it is a write to the card), so a move refused as `stale` is expected: if the refusal shows the card still in this self-review phase, retry once with the `expectedRevision` it names; if it shows the card in another phase, someone moved it, so leave it there. That phase takes the card only once Factory has attached the change request to it, which happens when the provider reports it opened. If the move is refused because the card has no pull request yet, wait briefly (`sleep 20`), re-read the revision from the latest `factory-phase` signal, and retry, up to three times; if it is still refused, the change request is tracked on its own card instead (a manual card, or an issue from another provider than the repository): the project's intake routes decide where that card goes. Post the change request link, say it is tracked on its own card and that a person should confirm it is reviewed there, and leave this card where it is.
|
|
64
64
|
|
|
65
65
|
Never move the card to a terminal phase yourself: the merge finishes it. Then post the report and the change request link as your final conversation message and stop.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mastra/factory",
|
|
3
|
-
"version": "0.28.0-alpha.
|
|
3
|
+
"version": "0.28.0-alpha.11",
|
|
4
4
|
"description": "Mastra Software Factory module: the server core behind the Mastra Software Factory — storage domains, integrations, and surfaces for agent-powered software delivery",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"publishConfig": {
|
|
@@ -60,9 +60,9 @@
|
|
|
60
60
|
"zod": "^4.6.7",
|
|
61
61
|
"@mastra/auth-studio": "1.4.0-alpha.1",
|
|
62
62
|
"@mastra/auth-workos": "1.6.8",
|
|
63
|
-
"@mastra/code-sdk": "1.19.0-alpha.
|
|
64
|
-
"@mastra/connect": "1.
|
|
65
|
-
"@mastra/core": "1.83.0-alpha.
|
|
63
|
+
"@mastra/code-sdk": "1.19.0-alpha.11",
|
|
64
|
+
"@mastra/connect": "1.4.0-alpha.4",
|
|
65
|
+
"@mastra/core": "1.83.0-alpha.9",
|
|
66
66
|
"@mastra/mcp": "2.9.0-alpha.3",
|
|
67
67
|
"@mastra/platform-workspace": "1.13.0-alpha.1",
|
|
68
68
|
"@mastra/slack": "1.9.0-alpha.0"
|
|
@@ -76,10 +76,10 @@
|
|
|
76
76
|
"@internal/lint": "0.0.148",
|
|
77
77
|
"@internal/types-builder": "0.0.123",
|
|
78
78
|
"@internal/workspace": "0.0.20",
|
|
79
|
-
"@mastra/deployer": "1.83.0-alpha.
|
|
80
|
-
"@mastra/libsql": "1.30.0-alpha.
|
|
81
|
-
"@mastra/pg": "1.36.0-alpha.
|
|
82
|
-
"@mastra/server": "1.83.0-alpha.
|
|
79
|
+
"@mastra/deployer": "1.83.0-alpha.9",
|
|
80
|
+
"@mastra/libsql": "1.30.0-alpha.3",
|
|
81
|
+
"@mastra/pg": "1.36.0-alpha.4",
|
|
82
|
+
"@mastra/server": "1.83.0-alpha.9"
|
|
83
83
|
},
|
|
84
84
|
"engines": {
|
|
85
85
|
"node": ">=22.19.0"
|