mlgym-deploy 3.3.43 → 3.3.44

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
@@ -60,7 +60,7 @@ cp ADD_TO_CURSOR_SETTINGS.json.example ADD_TO_CURSOR_SETTINGS.json
60
60
  "mcpServers": {
61
61
  "gitlab-backend": {
62
62
  "command": "node",
63
- "args": ["/your/absolute/path/to/gitlab_backend/mcp-server/index.js"],
63
+ "args": ["/your/absolute/path/to/mcp-server/index.js"],
64
64
  "env": {
65
65
  "GITLAB_BACKEND_URL": "https://backend.eu.ezb.net",
66
66
  "GITLAB_URL": "https://git.mlgym.io",
@@ -0,0 +1,230 @@
1
+ # NPM Release Procedure
2
+
3
+ This document describes how to publish the `mlgym-deploy` MCP server package to npm.
4
+
5
+ ## Prerequisites
6
+
7
+ - npm account with publish access to `mlgym-deploy` package
8
+ - npm access token (preferred method)
9
+ - Package version must be incremented before publishing
10
+
11
+ ## Authentication Methods
12
+
13
+ ### Method 1: Access Token (Recommended) ✅
14
+
15
+ Using an access token is **preferred** because:
16
+ - ✅ No 2FA/OTP required during publish
17
+ - ✅ Faster and more automated
18
+ - ✅ Works in CI/CD pipelines
19
+ - ✅ Can be revoked/rotated easily
20
+ - ✅ Suitable for scripted deployments
21
+
22
+ #### Setup Access Token
23
+
24
+ 1. **Configure token locally:**
25
+ ```bash
26
+ npm config set //registry.npmjs.org/:_authToken <YOUR_TOKEN>
27
+ ```
28
+
29
+ 2. **Verify authentication:**
30
+ ```bash
31
+ npm whoami
32
+ # Should output: chka_s5
33
+ ```
34
+
35
+ 3. **Publish:**
36
+ ```bash
37
+ cd mcp-server
38
+ npm publish
39
+ ```
40
+
41
+ ### Method 2: OTP/2FA (Alternative)
42
+
43
+ If you don't have an access token, you can use 2FA:
44
+
45
+ ```bash
46
+ npm publish --otp=<6-DIGIT-CODE>
47
+ ```
48
+
49
+ **Downsides:**
50
+ - Requires manual 2FA code entry each time
51
+ - Codes expire quickly (30 seconds)
52
+ - Not suitable for automation
53
+ - Slower workflow
54
+
55
+ ## Release Workflow
56
+
57
+ ### Step 1: Increment Version
58
+
59
+ Edit `mcp-server/package.json` and `mcp-server/index.js`:
60
+
61
+ ```json
62
+ {
63
+ "version": "3.3.44"
64
+ }
65
+ ```
66
+
67
+ ```javascript
68
+ const CURRENT_VERSION = '3.3.44'; // Update with change description
69
+ ```
70
+
71
+ ### Step 2: Update CHANGELOG (if exists)
72
+
73
+ Document what changed in this release.
74
+
75
+ ### Step 3: Commit Changes
76
+
77
+ ```bash
78
+ git add mcp-server/package.json mcp-server/index.js
79
+ git commit -m "Bump version to 3.3.44
80
+
81
+ - Description of changes
82
+ - What was fixed/added/improved"
83
+ ```
84
+
85
+ ### Step 4: Publish to npm
86
+
87
+ **Using Access Token (Recommended):**
88
+
89
+ ```bash
90
+ cd mcp-server
91
+ npm publish
92
+ ```
93
+
94
+ **Using OTP:**
95
+
96
+ ```bash
97
+ cd mcp-server
98
+ npm publish --otp=123456
99
+ ```
100
+
101
+ ### Step 5: Verify Publication
102
+
103
+ ```bash
104
+ # Check latest version
105
+ npm view mlgym-deploy version
106
+
107
+ # Check publication time
108
+ npm view mlgym-deploy time.modified
109
+
110
+ # Test installation
111
+ npm install -g mlgym-deploy@latest
112
+ mlgym-mcp --help
113
+ ```
114
+
115
+ ### Step 6: Tag Release (Optional)
116
+
117
+ ```bash
118
+ git tag -a v3.3.44 -m "Release v3.3.44"
119
+ git push origin v3.3.44
120
+ ```
121
+
122
+ ## NPM Access Token Management
123
+
124
+ ### Current Token
125
+
126
+ **Token:** `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`
127
+ **User:** chka_s5
128
+ **Scope:** Publish access to mlgym-deploy
129
+
130
+ ### Token Storage
131
+
132
+ **Local config (recommended for development):**
133
+ ```bash
134
+ npm config set //registry.npmjs.org/:_authToken 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
135
+ ```
136
+
137
+ **Per-project .npmrc (not recommended - security risk):**
138
+ ```
139
+ //registry.npmjs.org/:_authToken=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
140
+ ```
141
+ ⚠️ **Never commit .npmrc with tokens to git!**
142
+
143
+ **Environment variable (good for CI/CD):**
144
+ ```bash
145
+ export NPM_TOKEN=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
146
+ echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" > ~/.npmrc
147
+ ```
148
+
149
+ ### Revoking a Token
150
+
151
+ If token is compromised:
152
+
153
+ 1. Login to npmjs.com
154
+ 2. Go to Account Settings → Access Tokens
155
+ 3. Find the token and click "Delete"
156
+ 4. Generate a new token
157
+ 5. Update local config with new token
158
+
159
+ ## Common Issues
160
+
161
+ ### Issue: "npm ERR! code E404"
162
+
163
+ **Cause:** Package name doesn't exist or you don't have access
164
+ **Solution:** Verify package name and permissions
165
+
166
+ ### Issue: "npm ERR! code EOTP"
167
+
168
+ **Cause:** 2FA required but not provided
169
+ **Solution:** Use access token method instead of OTP
170
+
171
+ ### Issue: "npm ERR! 403 Forbidden"
172
+
173
+ **Cause:** Invalid or expired token
174
+ **Solution:** Regenerate access token
175
+
176
+ ### Issue: "Version already exists"
177
+
178
+ **Cause:** Version number in package.json hasn't been incremented
179
+ **Solution:** Bump version before publishing
180
+
181
+ ### Issue: "npm auto-corrected some errors"
182
+
183
+ **Cause:** package.json formatting issues
184
+ **Solution:** Run `npm pkg fix` and commit the changes
185
+
186
+ ## Automated CI/CD Publishing
187
+
188
+ For GitLab CI/CD pipeline:
189
+
190
+ ```yaml
191
+ publish_npm:
192
+ stage: publish
193
+ only:
194
+ - tags
195
+ script:
196
+ - cd mcp-server
197
+ - echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" > ~/.npmrc
198
+ - npm publish
199
+ variables:
200
+ NPM_TOKEN: $NPM_TOKEN # Set in GitLab CI/CD variables
201
+ ```
202
+
203
+ ## Version History
204
+
205
+ | Version | Date | SDK Version | Notable Changes |
206
+ |---------|------|-------------|-----------------|
207
+ | 3.3.43 | 2026-01-22 | 1.25.3 | SDK security upgrade, contact info |
208
+ | 3.3.42 | 2025-XX-XX | 0.6.1 | deploy_dollie tool |
209
+ | 3.0.0 | 2024-XX-XX | 0.6.0 | Monolithic workflows |
210
+
211
+ ## Quick Reference
212
+
213
+ ```bash
214
+ # Configure token (one-time setup)
215
+ npm config set //registry.npmjs.org/:_authToken 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
216
+
217
+ # Verify auth
218
+ npm whoami
219
+
220
+ # Publish
221
+ cd mcp-server && npm publish
222
+
223
+ # Verify publication
224
+ npm view mlgym-deploy version
225
+ ```
226
+
227
+ ---
228
+
229
+ **Last Updated:** 2026-01-22
230
+ **Maintainer:** chka_s5 (operations@stratus5.com)
package/index.js CHANGED
@@ -18,7 +18,7 @@ import crypto from 'crypto';
18
18
  const execAsync = promisify(exec);
19
19
 
20
20
  // Current version of this MCP server - INCREMENT FOR WORKFLOW FIXES
21
- const CURRENT_VERSION = '3.3.43'; // Add embedded contact info (operations@stratus5.com) and hide infrastructure URLs from help
21
+ const CURRENT_VERSION = '3.3.44'; // Update README with installation and configuration instructions
22
22
  const PACKAGE_NAME = 'mlgym-deploy';
23
23
 
24
24
  // Debug logging configuration - ENABLED BY DEFAULT
package/package.json CHANGED
@@ -1,11 +1,11 @@
1
1
  {
2
2
  "name": "mlgym-deploy",
3
- "version": "3.3.43",
3
+ "version": "3.3.44",
4
4
  "description": "MCP server for MLGym - Complete deployment management: deploy, configure, monitor, and rollback applications",
5
5
  "main": "index.js",
6
6
  "type": "module",
7
7
  "bin": {
8
- "mlgym-mcp": "./index.js"
8
+ "mlgym-mcp": "index.js"
9
9
  },
10
10
  "scripts": {
11
11
  "start": "node index.js"