Skip to content

Bump to 0.2.24 - #23

Merged
jbn2336mz merged 1 commit into
mainfrom
release/0.2.24
Sep 17, 2026
Merged

jbn2336mz merged 1 commit into
mainfrom
release/0.2.24

Conversation

@jbn2336mz

Copy link
Copy Markdown
Member

Releases the GitHub publishing tools from #22, which landed after the 0.2.23 bump and so are not in the published package.

Checked rather than assumed: the tarball on npm for 0.2.23 contains lib/history.js and lib/replay.js but no lib/github.js. A npm pack --dry-run here lists it at 32.3kB, so 0.2.24 carries it.

What reaches users with this

From #22, unreleased until now. Five tools that put a local mock on a public URL with no Mockzilla account, by pushing to a repository the user names and letting the action deploy it: check_github_deployable, list_github_repos, publish_to_github, wait_for_github_deploy, unpublish_from_github.

Already published in 0.2.23, listed for the release notes: request history and diagnostics, replay setup, and the 2.8.21 CLI pin.

Versions

package.json and server.json both to 0.2.24, in one commit, as every previous bump has done.

The CLI pin stays at 2.8.21, which is current.

Before publishing

make publish builds the docs first, so the tarball carries today's engine docs at the pinned version. Worth running make build and confirming docs/index.json reports engine_version: 2.8.21 if the docs bundle has changed since.

Tests

make smoke green against a 2.8.21 build: all six suites, including the sweep-covered local tools. A full sweep of every tool through the stdio bridge ran clean earlier on this code: 25 exercised, 0 failures, 10 skipped as outward-facing.

@jbn2336mz
jbn2336mz merged commit 48769f7 into main Sep 17, 2026
3 checks passed
@jbn2336mz
jbn2336mz deleted the release/0.2.24 branch September 17, 2026 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant