@denvermullets/jait 1.0.0 → 1.1.0

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 CHANGED
@@ -1,22 +1,3 @@
1
- ```bash
2
- claude mcp add my-server -- node /absolute/path/to/your/dist/index.js
3
- ```
4
-
5
- just have to remember to put
6
-
7
- ```json
8
- "mcpServers": {
9
- "mtasks": {
10
- "command": "node",
11
- "args": ["BUILD_FILE_LOCATION"],
12
- "env": {
13
- "MTASKS_API_URL": "",
14
- "MTASKS_API_TOKEN": ""
15
- }
16
- }
17
- }
18
- ```
19
-
20
1
  ## Install
21
2
 
22
3
  Install the published package from npm — no clone, no manual build.
@@ -65,4 +46,53 @@ npx -y @denvermullets/jait logout
65
46
  Both defaults can be overridden with environment variables, mostly useful for pointing at staging or localhost during development:
66
47
 
67
48
  - `MTASKS_API_URL` — overrides the default production URL.
68
- - `MTASKS_API_TOKEN` — overrides the saved token from `jait login`.
49
+ - `MTASKS_API_TOKEN` — overrides the saved token from `jait login`.
50
+
51
+
52
+ ----
53
+
54
+ #### old notes to remove later:
55
+ ```bash
56
+ claude mcp add my-server -- node /absolute/path/to/your/dist/index.js
57
+ ```
58
+
59
+ just have to remember to put
60
+
61
+ ```json
62
+ "mcpServers": {
63
+ "mtasks": {
64
+ "command": "node",
65
+ "args": ["BUILD_FILE_LOCATION"],
66
+ "env": {
67
+ "MTASKS_API_URL": "",
68
+ "MTASKS_API_TOKEN": ""
69
+ }
70
+ }
71
+ }
72
+ ```
73
+
74
+ ---
75
+
76
+ ## Release / publish notes (for maintainer)
77
+
78
+ Publishing a new version to npm. `npm version <type>` bumps `package.json`, commits, and tags in one shot — use it after merging to `main` so the tag points at the merge commit.
79
+
80
+ ```bash
81
+ # from main, after your PR is merged
82
+ git checkout main && git pull
83
+
84
+ npm version patch # 1.0.1 → 1.0.2 (bug fixes)
85
+ npm version minor # 1.0.1 → 1.1.0 (new features, backwards compatible)
86
+ npm version major # 1.0.1 → 2.0.0 (breaking changes)
87
+
88
+ git push && git push --tags
89
+ npm publish
90
+ ```
91
+
92
+ If you hand-tagged already (`git tag v1.0.1`) and then `npm publish` fails with "cannot publish over previously published versions", it means you forgot to bump `package.json`. Either edit the version manually and commit, or drop the tag and use `npm version` as above.
93
+
94
+ Verify after publish:
95
+ ```bash
96
+ npm view @denvermullets/jait
97
+ npx -y @denvermullets/jait@latest --help # sanity check the bin still works
98
+ ```
@@ -6,6 +6,9 @@ const projectStatusEnum = z
6
6
  const priorityEnum = z
7
7
  .enum(["urgent", "high", "medium", "low", "no_priority"])
8
8
  .describe("Priority level");
9
+ const roadmapCommitmentEnum = z
10
+ .enum(["now", "next", "later"])
11
+ .describe('Roadmap commitment lane: "now" (shipping in ~6 weeks), "next" (up after Now), "later" (on the radar). Omit to leave unchanged; pass null to remove from roadmap.');
9
12
  function formatProject(project, detailed = false) {
10
13
  const lines = [
11
14
  `**${project.name}** — ID: ${project.id}`,
@@ -19,6 +22,8 @@ function formatProject(project, detailed = false) {
19
22
  lines.push(` Start: ${project.start_date}`);
20
23
  if (project.due_date)
21
24
  lines.push(` Due: ${project.due_date}`);
25
+ if (project.roadmap_commitment)
26
+ lines.push(` Roadmap: ${project.roadmap_commitment}`);
22
27
  if (detailed) {
23
28
  if (project.milestone)
24
29
  lines.push(` Milestone: ${project.milestone.name}`);
@@ -65,7 +70,8 @@ export function registerProjectTools(server) {
65
70
  .optional()
66
71
  .describe("Due date in YYYY-MM-DD format"),
67
72
  label_ids: z.array(z.number()).optional().describe("Label IDs"),
68
- }, async ({ team_id, name, description, status, priority, lead_id, milestone_id, start_date, due_date, label_ids, }) => {
73
+ roadmap_commitment: roadmapCommitmentEnum.optional(),
74
+ }, async ({ team_id, name, description, status, priority, lead_id, milestone_id, start_date, due_date, label_ids, roadmap_commitment, }) => {
69
75
  const project = await apiRequest(`/api/v1/teams/${team_id}/projects`, {
70
76
  method: "POST",
71
77
  body: {
@@ -79,6 +85,7 @@ export function registerProjectTools(server) {
79
85
  start_date,
80
86
  due_date,
81
87
  label_ids,
88
+ roadmap_commitment,
82
89
  },
83
90
  },
84
91
  });
@@ -109,7 +116,8 @@ export function registerProjectTools(server) {
109
116
  .optional()
110
117
  .describe("Due date in YYYY-MM-DD format"),
111
118
  label_ids: z.array(z.number()).optional().describe("Set label IDs"),
112
- }, async ({ team_id, project_id, name, description, status, priority, lead_id, milestone_id, start_date, due_date, label_ids, }) => {
119
+ roadmap_commitment: roadmapCommitmentEnum.nullable().optional(),
120
+ }, async ({ team_id, project_id, name, description, status, priority, lead_id, milestone_id, start_date, due_date, label_ids, roadmap_commitment, }) => {
113
121
  const fields = {};
114
122
  if (name !== undefined)
115
123
  fields.name = name;
@@ -129,6 +137,8 @@ export function registerProjectTools(server) {
129
137
  fields.due_date = due_date;
130
138
  if (label_ids !== undefined)
131
139
  fields.label_ids = label_ids;
140
+ if (roadmap_commitment !== undefined)
141
+ fields.roadmap_commitment = roadmap_commitment;
132
142
  const project = await apiRequest(`/api/v1/teams/${team_id}/projects/${project_id}`, {
133
143
  method: "PATCH",
134
144
  body: { project: fields },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@denvermullets/jait",
3
- "version": "1.0.0",
3
+ "version": "1.1.0",
4
4
  "description": "MCP server for Just Another Issue Tracker",
5
5
  "type": "module",
6
6
  "bin": {