npm - executor - Versions diffs - 1.1.10-beta.5 → 1.2.0-beta.7 - Mend

executor 1.1.10-beta.5 → 1.2.0-beta.7

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 (15) hide show

package/README.md +8 -5
package/bin/executor.mjs +34395 -22221
package/package.json +1 -1
package/resources/web/assets/{highlighted-body-TPN3WLV5-CNtoUE2O.js → highlighted-body-TPN3WLV5-BA0VsxbD.js} +1 -1
package/resources/web/assets/{index-Dyhx5qgf.js → index-0GhKTMbx.js} +2 -2
package/resources/web/assets/mermaid-O7DHMXV3-Bca_0pLy.js +658 -0
package/resources/web/assets/mermaid-O7DHMXV3-BssdgemB.css +1 -0
package/resources/web/index.html +1 -1
package/bin/impl/edit.js +0 -201
package/bin/impl/format.js +0 -275
package/bin/impl/parser.js +0 -682
package/bin/impl/scanner.js +0 -456
package/bin/impl/string-intern.js +0 -42
package/resources/web/assets/mermaid-O7DHMXV3-CfqEcqYS.js +0 -658
package/resources/web/assets/mermaid-O7DHMXV3-D1toCiZx.css +0 -1

package/README.md CHANGED Viewed

@@ -324,14 +324,17 @@ If you are exploring the repo, these are the directories that matter most:
 ## Releasing
-- `bun run release:beta` is the simplest beta flow. It bumps `apps/executor/package.json`, runs the local publish dry-run, commits, pushes the branch, pushes the matching tag, and lets GitHub Actions publish it.
-- `bun run release:beta:dry-run` prints the next beta version and the exact git actions without changing anything.
-- `bun run --cwd apps/executor release:publish` is the only supported publish command.
+- Add a changeset in any PR that should release: `bun run changeset`.
+- Merge that PR to `main`. `.github/workflows/release.yml` opens or updates a `Version Packages` release PR for version bumps and changelog updates.
+- Merge the `Version Packages` PR. The release workflow pushes the matching git tag and dispatches `.github/workflows/publish-executor-package.yml`, which publishes to npm and creates the GitHub release.
+- Do not edit `apps/executor/package.json` by hand for normal releases. Changesets owns the version.
+- For a beta train, enter prerelease mode with `bun run release:beta:start`, commit `.changeset/pre.json`, and merge it. Release PRs will then use `-beta.x` versions until you exit with `bun run release:beta:stop`.
+- `bun run --cwd apps/executor release:publish` remains the publish implementation used by CI.
+- To build and pack the publish artifact locally without publishing, run `bun run --cwd apps/executor release:publish:dry-run`.
+- `.github/workflows/publish-executor-package.yml` can also be run manually with a tag input if a publish needs to be retried for an already-created version tag.
 - One-time npm setup: either configure npm trusted publishing for `RhysSullivan/executor` with the workflow file `.github/workflows/publish-executor-package.yml`, or add a GitHub Actions secret named `NPM_TOKEN` that can publish the `executor` package.
 - Stable releases use a normal semver like `1.2.3` and publish to npm under `latest`.
 - Beta releases use a prerelease semver like `1.3.0-beta.1` and publish to npm under `beta`.
-- Push a matching git tag such as `v1.2.3` or `v1.3.0-beta.1` to trigger `.github/workflows/publish-executor-package.yml`.
-- To build and pack the publish artifact locally without publishing, run `bun run --cwd apps/executor release:publish:dry-run`.
 ## Project status