eve-online-mcp 0.2.0 → 0.2.1
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 +1 -1
- package/package.json +7 -7
package/README.md
CHANGED
|
@@ -178,7 +178,7 @@ Review any new non-GET operation manually. Read-only `POST` routes are deliberat
|
|
|
178
178
|
|
|
179
179
|
## Publishing to npm
|
|
180
180
|
|
|
181
|
-
[`release.yml`](.github/workflows/release.yml) runs on every push to `main
|
|
181
|
+
[`release.yml`](.github/workflows/release.yml) runs on every push to `main` and on explicit dispatches from the maintenance automation. Release Please maintains a release pull request using Conventional Commit history; use subjects such as `fix: repair release workflow` or `feat: add route planning`. Dependabot uses `fix(deps):` and `fix(deps-dev):` subjects so dependency maintenance produces patch releases. A verified release pull request from the dedicated release app is approved and squash-merged automatically after required checks pass. That pull request updates `package.json`, `package-lock.json`, and `CHANGELOG.md` together. Merging it creates the matching Git tag and GitHub Release, then validates and packs the project inside the devcontainer and publishes that exact version to npm. A guarded assertion compares the release version, Git tag, and the tagged `package.json` before publishing. The workflow also bootstraps an existing matching GitHub Release when its package version is still absent from npm.
|
|
182
182
|
|
|
183
183
|
Publishing uses npm trusted publishing through GitHub OIDC and produces provenance. On npm, configure the trusted publisher as repository `HammoTime/eve-online-mcp`, workflow `release.yml`, with direct publishing allowed. Because an unclaimed package cannot have trusted publishing configured yet, its first release requires a granular npm automation token stored as the `NPM_TOKEN` GitHub secret. That one-time bootstrap publish does not request provenance, which also permits recovery of a historical tag whose repository metadata predates the current GitHub owner. After the initial publish, configure trusted publishing and remove the secret; subsequent OIDC releases publish provenance.
|
|
184
184
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "eve-online-mcp",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.1",
|
|
4
4
|
"description": "Read-only MCP access to the complete EVE Online ESI OpenAPI surface",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"eve-online",
|
|
@@ -51,20 +51,20 @@
|
|
|
51
51
|
"license": "AGPL-3.0-only",
|
|
52
52
|
"dependencies": {
|
|
53
53
|
"@modelcontextprotocol/server": "^2.0.0",
|
|
54
|
-
"open": "^
|
|
54
|
+
"open": "^11.0.2",
|
|
55
55
|
"zod": "^4.0.0"
|
|
56
56
|
},
|
|
57
57
|
"devDependencies": {
|
|
58
|
-
"@eslint/js": "^
|
|
58
|
+
"@eslint/js": "^10.0.1",
|
|
59
59
|
"@modelcontextprotocol/client": "^2.0.0",
|
|
60
|
-
"@types/node": "^
|
|
61
|
-
"@vitest/coverage-v8": "^
|
|
62
|
-
"eslint": "^9.
|
|
60
|
+
"@types/node": "^26.4.1",
|
|
61
|
+
"@vitest/coverage-v8": "^4.1.11",
|
|
62
|
+
"eslint": "^10.9.1",
|
|
63
63
|
"eslint-config-prettier": "^10.0.0",
|
|
64
64
|
"prettier": "^3.0.0",
|
|
65
65
|
"tsx": "^4.0.0",
|
|
66
66
|
"typescript": "^6.0.0",
|
|
67
67
|
"typescript-eslint": "^8.0.0",
|
|
68
|
-
"vitest": "^
|
|
68
|
+
"vitest": "^4.1.11"
|
|
69
69
|
}
|
|
70
70
|
}
|