agent-comms/release.config.ts at main · ExaDev/agent-comms · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
import type { GlobalConfig } from "semantic-release";

const config: GlobalConfig = {
  branches: ["main"],
  plugins: [
    [
      "@semantic-release/commit-analyzer",
      {
        preset: "conventionalcommits",
        releaseRules: [
          { type: "feat", release: "minor" },
          { type: "fix", release: "patch" },
          { type: "refactor", release: "patch" },
          { type: "perf", release: "patch" },
          { type: "docs", release: "patch" },
          { type: "style", release: "patch" },
          { type: "test", release: "patch" },
          { type: "build", release: "patch" },
          { type: "ci", release: "patch" },
          { type: "chore", release: "patch" },
          { breaking: true, release: "major" },
        ],
      },
    ],
    [
      "@semantic-release/release-notes-generator",
      {
        preset: "conventionalcommits",
        presetConfig: {
          types: [
            { type: "feat", section: "Features" },
            { type: "fix", section: "Bug Fixes" },
            { type: "refactor", section: "Refactoring" },
            { type: "perf", section: "Performance" },
            { type: "docs", section: "Documentation" },
            { type: "style", section: "Styles" },
            { type: "test", section: "Tests" },
            { type: "build", section: "Build" },
            { type: "ci", section: "CI" },
            { type: "chore", section: "Chores" },
          ],
        },
      },
    ],
    "@semantic-release/changelog",
    "@semantic-release/npm",
    // The MCP registry publish is deliberately not a publish step here: semantic-release stops at the first failing publish step, so a registry outage that outlasted the retry budget (run 39670379457, v8.15.4) left the version on npm and tagged with no GitHub release. The registry publish is its own CI job after the release (the `registry` job in ci.yml), where an outage fails only that job, which can be re-run and skips a version the registry already lists.
    [
      "@semantic-release/exec",
      {
        prepareCmd: "tsx scripts/sync-release-metadata.ts",
      },
    ],
    [
      "@semantic-release/git",
      {
        assets: [
          "package.json",
          "pnpm-lock.yaml",
          ".claude-plugin/plugin.json",
          ".claude-plugin/marketplace.json",
          "server.json",
          "CHANGELOG.md",
        ],
        message: "chore(release): v${nextRelease.version} [skip ci]",
      },
    ],
    "@semantic-release/github",
  ],
};

export default config;