domain-search-mcp 1.2.24 → 1.2.26

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.
@@ -0,0 +1,56 @@
1
+ name-template: "v$RESOLVED_VERSION"
2
+ tag-template: "v$RESOLVED_VERSION"
3
+
4
+ categories:
5
+ - title: "Breaking Changes"
6
+ labels:
7
+ - "breaking"
8
+ - title: "Features"
9
+ labels:
10
+ - "feature"
11
+ - "enhancement"
12
+ - title: "Fixes"
13
+ labels:
14
+ - "fix"
15
+ - "bug"
16
+ - title: "Docs"
17
+ labels:
18
+ - "docs"
19
+ - title: "Chore"
20
+ labels:
21
+ - "chore"
22
+ - "refactor"
23
+ - title: "Security"
24
+ labels:
25
+ - "security"
26
+
27
+ change-template: "- $TITLE (#$NUMBER) by @$AUTHOR"
28
+
29
+ version-resolver:
30
+ major:
31
+ labels:
32
+ - "breaking"
33
+ minor:
34
+ labels:
35
+ - "feature"
36
+ - "enhancement"
37
+ patch:
38
+ labels:
39
+ - "fix"
40
+ - "bug"
41
+ - "docs"
42
+ - "chore"
43
+ - "refactor"
44
+ - "security"
45
+ default: patch
46
+
47
+ exclude-labels:
48
+ - "skip-changelog"
49
+
50
+ template: |
51
+ ## What's Changed
52
+
53
+ $CHANGES
54
+
55
+ ## Full Changelog
56
+ https://github.com/dorukardahan/domain-search-mcp/compare/$PREVIOUS_TAG...v$RESOLVED_VERSION
@@ -0,0 +1,27 @@
1
+ name: Release Drafter
2
+
3
+ on:
4
+ push:
5
+ branches:
6
+ - main
7
+ pull_request:
8
+ types:
9
+ - opened
10
+ - reopened
11
+ - synchronize
12
+ - labeled
13
+ - unlabeled
14
+ - ready_for_review
15
+
16
+ permissions:
17
+ contents: write
18
+ pull-requests: write
19
+
20
+ jobs:
21
+ update_release_draft:
22
+ runs-on: ubuntu-latest
23
+ steps:
24
+ - name: Update release draft
25
+ uses: release-drafter/release-drafter@v6
26
+ env:
27
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
@@ -0,0 +1,43 @@
1
+ name: Release
2
+
3
+ on:
4
+ push:
5
+ tags:
6
+ - "v*.*.*"
7
+ workflow_dispatch:
8
+
9
+ permissions:
10
+ contents: write
11
+ id-token: write
12
+
13
+ jobs:
14
+ publish:
15
+ runs-on: ubuntu-latest
16
+ steps:
17
+ - name: Checkout
18
+ uses: actions/checkout@v4
19
+
20
+ - name: Setup Node
21
+ uses: actions/setup-node@v4
22
+ with:
23
+ node-version: 18
24
+ registry-url: https://registry.npmjs.org
25
+
26
+ - name: Install deps
27
+ run: npm ci
28
+
29
+ - name: Build
30
+ run: npm run build
31
+
32
+ - name: Publish (provenance)
33
+ run: npm publish --provenance
34
+ env:
35
+ NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
36
+
37
+ - name: Publish release notes
38
+ uses: release-drafter/release-drafter@v6
39
+ with:
40
+ publish: true
41
+ tag: ${{ github.ref_name }}
42
+ env:
43
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
package/CHANGELOG.md ADDED
@@ -0,0 +1,37 @@
1
+ # Changelog
2
+
3
+ All notable changes to this project will be documented in this file.
4
+
5
+ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
+ and this project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
+
8
+ ## [Unreleased]
9
+ ### Added
10
+ - -
11
+
12
+ ## [1.2.26] - 2025-12-30
13
+ ### Added
14
+ - Release Drafter automation for release notes (labels -> changelog).
15
+
16
+ ## [1.2.25] - 2025-12-30
17
+ ### Added
18
+ - GitHub Actions release workflow that publishes with provenance and creates GitHub Releases.
19
+
20
+ ## [1.2.24] - 2025-12-30
21
+ ### Added
22
+ - Release workflow documentation and local publish scripts (canary/latest).
23
+
24
+ ## [1.2.23] - 2025-12-30
25
+ ### Added
26
+ - Sedo public feed lookup for aftermarket auction hints (configurable TTL + feed URL).
27
+
28
+ ## [1.2.22] - 2025-12-30
29
+ ### Changed
30
+ - Removed Dynadot backend usage due to ToS restrictions.
31
+
32
+ [Unreleased]: https://github.com/dorukardahan/domain-search-mcp/compare/v1.2.26...HEAD
33
+ [1.2.26]: https://github.com/dorukardahan/domain-search-mcp/compare/v1.2.25...v1.2.26
34
+ [1.2.25]: https://github.com/dorukardahan/domain-search-mcp/compare/v1.2.24...v1.2.25
35
+ [1.2.24]: https://github.com/dorukardahan/domain-search-mcp/compare/v1.2.23...v1.2.24
36
+ [1.2.23]: https://github.com/dorukardahan/domain-search-mcp/compare/v1.2.22...v1.2.23
37
+ [1.2.22]: https://github.com/dorukardahan/domain-search-mcp/compare/v1.2.21...v1.2.22
package/README.md CHANGED
@@ -188,7 +188,12 @@ npm run build # compile to dist/
188
188
 
189
189
  ## Release
190
190
 
191
- See `docs/RELEASE.md` for the canary -> latest publish flow with provenance.
191
+ See `docs/RELEASE.md` for the canary -> latest publish flow. Tags like `v1.2.24`
192
+ trigger GitHub Releases + npm publish via CI.
193
+
194
+ ## Changelog
195
+
196
+ See `CHANGELOG.md` for release history.
192
197
 
193
198
  ## Security Notes
194
199
 
package/docs/RELEASE.md CHANGED
@@ -5,10 +5,13 @@ Use this flow to publish safely and keep MCP clients stable.
5
5
  ## Checklist
6
6
 
7
7
  - Bump versions in `package.json`, `package-lock.json`, and `server.json`.
8
+ - Update `CHANGELOG.md` (add a new version section).
8
9
  - Run `npm run test` (or at least `npm run build`).
10
+ - Ensure GitHub secret `NPM_TOKEN` is set (used by CI).
11
+ - Label PRs so Release Drafter can generate clean notes (see below).
9
12
  - Confirm no secrets are included in the package (`npm pack --dry-run` if needed).
10
13
 
11
- ## Canary Publish
14
+ ## Canary Publish (Local)
12
15
 
13
16
  Publish a canary build for quick validation:
14
17
 
@@ -18,7 +21,7 @@ npm run release:canary
18
21
 
19
22
  Smoke test the canary in a local MCP client. If it behaves correctly, promote it.
20
23
 
21
- ## Promote to Latest
24
+ ## Promote to Latest (Local)
22
25
 
23
26
  ```bash
24
27
  npm run release:promote-latest
@@ -30,8 +33,31 @@ Or publish directly as latest:
30
33
  npm run release:latest
31
34
  ```
32
35
 
36
+ ## CI Release (Recommended)
37
+
38
+ Create a git tag and push it. CI will publish with provenance and create a GitHub Release:
39
+
40
+ ```bash
41
+ git tag v1.2.24
42
+ git push origin v1.2.24
43
+ ```
44
+
45
+ ## Release Drafter Labels
46
+
47
+ Use these labels so release notes are auto-generated cleanly:
48
+
49
+ - `breaking`
50
+ - `feature`, `enhancement`
51
+ - `fix`, `bug`
52
+ - `docs`
53
+ - `chore`, `refactor`
54
+ - `security`
55
+
56
+ Use `skip-changelog` to exclude a PR from release notes.
57
+
33
58
  ## Notes
34
59
 
35
- - All publish scripts use `--provenance` for supply-chain integrity.
60
+ - CI publishes with `--provenance` for supply-chain integrity.
61
+ - Local scripts use `--provenance` if supported; otherwise publish without provenance.
36
62
  - Prefer canary first for risky changes (protocol updates, new tool outputs).
37
63
  - If a release is bad, use `npm deprecate` and promote the previous version.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "domain-search-mcp",
3
- "version": "1.2.24",
3
+ "version": "1.2.26",
4
4
  "mcpName": "io.github.dorukardahan/domain-search-mcp",
5
5
  "description": "Fast domain availability MCP server. RDAP/WHOIS availability with backend pricing (Porkbun) and smart suggestions.",
6
6
  "main": "dist/server.js",
package/server.json CHANGED
@@ -6,12 +6,12 @@
6
6
  "url": "https://github.com/dorukardahan/domain-search-mcp",
7
7
  "source": "github"
8
8
  },
9
- "version": "1.2.24",
9
+ "version": "1.2.26",
10
10
  "packages": [
11
11
  {
12
12
  "registryType": "npm",
13
13
  "identifier": "domain-search-mcp",
14
- "version": "1.2.24",
14
+ "version": "1.2.26",
15
15
  "transport": {
16
16
  "type": "stdio"
17
17
  },