@taiga-ai/mcp-server 0.28.0-dev.590 → 0.28.0-dev.591
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/dist/index.js +8 -0
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -23162,6 +23162,14 @@ const TURN_EVENT_TRIGGERS = [
|
|
|
23162
23162
|
"changes_answered"
|
|
23163
23163
|
];
|
|
23164
23164
|
/**
|
|
23165
|
+
* The events the feed reads beside the turn log (PRO-3156): a board move and
|
|
23166
|
+
* a stop cleared. They carry no possession (`turn` is null), so they are not
|
|
23167
|
+
* turn triggers; the page decides which of them it shows -- a person's move,
|
|
23168
|
+
* a person's Resume.
|
|
23169
|
+
*/
|
|
23170
|
+
const ACTIVITY_EVENT_TYPES = ["state_changed", "needs_human_cleared"];
|
|
23171
|
+
[...TURN_EVENT_TRIGGERS, ...ACTIVITY_EVENT_TYPES];
|
|
23172
|
+
/**
|
|
23165
23173
|
* The two blocking states are NOT the same kind of blocker, and collapsing them
|
|
23166
23174
|
* into one list is what caused a bug in each direction (PRO-1028, PRO-1039).
|
|
23167
23175
|
* They are separate constants so the difference is data a reader can see rather
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@taiga-ai/mcp-server",
|
|
3
|
-
"version": "0.28.0-dev.
|
|
3
|
+
"version": "0.28.0-dev.591",
|
|
4
4
|
"description": "Taiga for AI coding assistants: read products, policies, initiatives and runs, and operate the line, over MCP",
|
|
5
5
|
"mcpName": "ga.tai/mcp-server",
|
|
6
6
|
"license": "UNLICENSED",
|