@rmartz/bot-automerge 1.0.2 → 1.0.3

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 (2) hide show
  1. package/README.md +14 -10
  2. package/package.json +2 -1
package/README.md CHANGED
@@ -65,16 +65,20 @@ pnpm run test # vitest
65
65
 
66
66
  ## Releases
67
67
 
68
- Versioned by [semantic-release](.releaserc.json). A push to `main` analyzes the
69
- Conventional-Commit history since the last `bot-automerge-v*` tag and, when a
70
- release is warranted, publishes the package to npmjs (public, via OIDC trusted
71
- publishing with provenance — no npm token) and creates the git tag + GitHub
72
- Release. Versions up to 0.2.1 were published to GitHub Packages and stay there for
73
- existing pins; new versions go to npmjs only. There is no release PR and no
74
- commit-back, so the
75
- built-in `GITHUB_TOKEN` suffices. `tagFormat` stays `bot-automerge-v${version}`
76
- for continuity with the prior release-please tags. A `Release dry-run` CI job
77
- validates the semantic-release config (that the changelog toolchain renders) on
68
+ Versioned by [semantic-release](.releaserc.json), run through the fleet's shared
69
+ [rmartz/semantic-release-ci](https://github.com/rmartz/semantic-release-ci)
70
+ workflow. A push to `main` analyzes the Conventional-Commit history since the
71
+ last `bot-automerge-v*` tag and, when a release is warranted, publishes the
72
+ package to npmjs (public, via OIDC trusted publishing with provenance — no npm
73
+ token) and creates the git tag + GitHub Release. The package is published
74
+ **before** the tag is pushed, so a failed publish never leaves a tag with no
75
+ package. Versions up to 0.2.1 were published to GitHub Packages and stay there
76
+ for existing pins; new versions go to npmjs only. `bot-automerge-v1.0.0` is a tag
77
+ with no package (its publish failed after tagging); use 1.0.1 or later. There is
78
+ no release PR and no commit-back, so the built-in `GITHUB_TOKEN` suffices.
79
+ `tagFormat` stays `bot-automerge-v${version}` for continuity with the prior
80
+ release-please tags. The shared `release-check / release-check` check validates
81
+ the semantic-release config (that commits analyze and the changelog renders) on
78
82
  every PR, so a broken release setup is caught before merge rather than on the
79
83
  post-merge release run.
80
84
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rmartz/bot-automerge",
3
- "version": "1.0.2",
3
+ "version": "1.0.3",
4
4
  "description": "Enables GitHub-native auto-merge for trustworthy bot pull requests (Dependabot patch/minor bumps and release-please release PRs), distributed via rmartz/bot-automerge-action.",
5
5
  "keywords": [
6
6
  "ci",
@@ -49,6 +49,7 @@
49
49
  "test:watch": "vitest"
50
50
  },
51
51
  "devDependencies": {
52
+ "@semantic-release/exec": "^7.1.0",
52
53
  "@types/node": "^26.6.2",
53
54
  "@typescript-eslint/eslint-plugin": "^8.70.0",
54
55
  "@typescript-eslint/parser": "^8.70.0",