next-issue 2.1.0 → 2.3.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 (2) hide show
  1. package/README.md +2 -1
  2. package/package.json +4 -3
package/README.md CHANGED
@@ -445,7 +445,8 @@ workflow reads the commits since the last tag and picks the bump: `feat` gives a
445
445
  minor, `fix` gives a patch, and a `!` mark or a `BREAKING CHANGE` body gives a
446
446
  major. Any other type releases nothing.
447
447
 
448
- The workflow then bumps the version and publishes the package to npm with a
448
+ The workflow then gives `next-issue` and `@ravshansbox/pi-next-issue` the same
449
+ new version and publishes both packages to npm with a
449
450
  [trusted publish](https://docs.npmjs.com/trusted-publishers), so no token is
450
451
  stored. Only after the publish does it push the tag and make the GitHub release,
451
452
  so a failed publish leaves no half-release behind. A manual run of the workflow
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "next-issue",
3
- "version": "2.1.0",
3
+ "version": "2.3.0",
4
4
  "description": "Autonomous issue harness driven by the pi SDK",
5
5
  "keywords": [
6
6
  "github",
@@ -10,11 +10,12 @@
10
10
  "automation",
11
11
  "cli"
12
12
  ],
13
- "homepage": "https://github.com/ravshansbox/next-issue#readme",
13
+ "homepage": "https://github.com/ravshansbox/next-issue/tree/main/packages/next-issue#readme",
14
14
  "bugs": "https://github.com/ravshansbox/next-issue/issues",
15
15
  "repository": {
16
16
  "type": "git",
17
- "url": "git+https://github.com/ravshansbox/next-issue.git"
17
+ "url": "git+https://github.com/ravshansbox/next-issue.git",
18
+ "directory": "packages/next-issue"
18
19
  },
19
20
  "license": "MIT",
20
21
  "author": "ravshansbox",