@dakaio/domainscout-mcp 1.5.1 → 2.0.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.
Files changed (4) hide show
  1. package/CHANGELOG.md +63 -0
  2. package/README.md +11 -9
  3. package/npm-shrinkwrap.json +3054 -0
  4. package/package.json +2 -1
package/CHANGELOG.md ADDED
@@ -0,0 +1,63 @@
1
+ # Changelog
2
+
3
+ Every release of `@dakaio/domainscout-mcp`, newest first. Each line is a merged pull request.
4
+
5
+ ## 2.0.0 - 2026-10-09
6
+
7
+ ### Features
8
+
9
+ - Release on every merge, by the pull request's title, with a changelog in the package ([#23](https://github.com/JohnDaka/domainscout-mcp/pull/23))
10
+
11
+ ## 1.5.2 - 2026-10-09
12
+
13
+ ### Fixes
14
+
15
+ - Publish with npm 11, the shrinkwrap made from package-lock.json ([#20](https://github.com/JohnDaka/domainscout-mcp/pull/20))
16
+
17
+ ## 1.5.1 - 2026-10-09
18
+
19
+ ### Fixes
20
+
21
+ - Each landing release asks for its own stylesheet and scripts ([#16](https://github.com/JohnDaka/domainscout-mcp/pull/16))
22
+
23
+ ### Other
24
+
25
+ - Lockfiles for the Claude plugin directory ([#18](https://github.com/JohnDaka/domainscout-mcp/pull/18))
26
+
27
+ ## 1.5.0 - 2026-10-09
28
+
29
+ ### Features
30
+
31
+ - An MCP Apps results card for check_domains ([#14](https://github.com/JohnDaka/domainscout-mcp/pull/14))
32
+
33
+ ### Fixes
34
+
35
+ - Removed the hand-written version badge from the landing page ([#12](https://github.com/JohnDaka/domainscout-mcp/pull/12))
36
+
37
+ ## 1.4.0 - 2026-10-08
38
+
39
+ ### Fixes
40
+
41
+ - Listed the tool's schemas without a draft-07 dialect ([#10](https://github.com/JohnDaka/domainscout-mcp/pull/10))
42
+
43
+ ## 1.3.0 - 2026-10-08
44
+
45
+ ### Features
46
+
47
+ - Server icon, privacy policy and a Claude plugin ([#7](https://github.com/JohnDaka/domainscout-mcp/pull/7))
48
+
49
+ ## 1.2.0 - 2026-10-08
50
+
51
+ ### Fixes
52
+
53
+ - Wrapped long report lines and showed the download on the Claude button ([#5](https://github.com/JohnDaka/domainscout-mcp/pull/5))
54
+
55
+ ## 1.1.2 - 2026-10-07
56
+
57
+ ### Features
58
+
59
+ - Added npm run bump and bump:site ([#3](https://github.com/JohnDaka/domainscout-mcp/pull/3))
60
+ - One command raises the version everywhere
61
+ - Added MCP Registry, Claude Desktop and catalog listings ([#2](https://github.com/JohnDaka/domainscout-mcp/pull/2))
62
+ - Added landing page releases by landing-v tags ([#1](https://github.com/JohnDaka/domainscout-mcp/pull/1))
63
+ - Added DomainScout, an MCP server for bulk domain search
package/README.md CHANGED
@@ -289,17 +289,19 @@ npm run build
289
289
  | `src/scout/`, `src/server/`, `src/cli/` | The check as a whole, the MCP server and the command line |
290
290
  | `test/` | Vitest tests; the network is faked, except for a local WHOIS server |
291
291
  | `examples/` | Real output of the tool |
292
- | `site/` | The landing page at domainscout.dakaio.com: static HTML, released by a `landing-v<version>` tag (`npm --prefix site run release`) |
292
+ | `site/` | The landing page at domainscout.dakaio.com: static HTML, put out on every change merged into `main` |
293
293
  | `server.json`, `manifest.json`, `glama.json` | Listings: the MCP Registry, the Claude Desktop extension, Glama |
294
294
 
295
- Releases: raise the version in a pull request with `npm run bump patch` (or `minor`, or an exact
296
- version such as `npm run bump 1.2.0`); it updates `package.json`, `npm-shrinkwrap.json`,
297
- `manifest.json` and `server.json` together. Then run `npm run release` on the merged `main`. It pushes the tag `v<version>`, and
298
- `.github/workflows/publish.yml` publishes to npm (trusted publishing), creates a GitHub Release
299
- with the Claude Desktop extension and publishes to the MCP Registry. Once the version is on npm,
300
- `npm run plugin` points the Claude plugin at it, with a lockfile, in a pull request of its own.
301
- The landing page goes out the
302
- same way: `npm run bump:site patch` in a pull request, then `npm --prefix site run release`.
295
+ Releases happen on merge. A pull request's title says what it is (`feat: …`, `fix: …`,
296
+ `docs: …`, `feat!: …`; `.github/workflows/pr-title.yml` checks it), and once it is merged into
297
+ `main`, `.github/workflows/publish.yml` decides: `feat` raises the minor version, `fix` and
298
+ `perf` the patch version, a `!` or "BREAKING CHANGE" the major one, and anything else, or a
299
+ change to nothing the package ships, releases nothing. A release raises the version in
300
+ `package.json`, `manifest.json` and `server.json`, adds the merged pull requests to
301
+ [CHANGELOG.md](CHANGELOG.md), tags it, publishes to npm (trusted
302
+ publishing), creates a GitHub Release with the Claude Desktop extension, publishes to the MCP
303
+ Registry and points the Claude plugin at the new version with a lockfile, committing to `main`
304
+ as it goes. The landing page goes out on every change to `site/` (`.github/workflows/landing.yml`).
303
305
 
304
306
  ## License
305
307