Skip to content

Prep for release 1.2.0 #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
richardcocks merged 2 commits into from
Aug 19, 2026
Merged

Prep for release 1.2.0 #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
51936ea
Prep for release 1.2.0
richardcocks Aug 19, 2026
ba926a1
Update CHANGELOG.md
richardcocks Aug 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 17 additions & 17 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,22 +1,22 @@
# Changelog

## Unreleased

Watch mode now runs on the JavaScript target (Node and Deno), so
`gleam run --target javascript -m vouch -- watch` works without the BEAM
installed. Quitting is Ctrl+C on JavaScript (q then Enter on Erlang stays
as it was). Deno projects using watch mode need `allow_run = ["gleam"]` in
their `gleam.toml`.

The inner test runs now follow the watcher's own target by default;
pass `--target=erlang|javascript` after the `--` to run them on a
different target than the watcher. Both `--target=x` and `--target x`
spellings are accepted, matching gleam's own flag.

On the JavaScript host, watch mode now has the core Jest/Vitest keys:
Enter forces a rerun, `a` runs the whole suite, `q` (or Ctrl+C) quits —
single keypress, no Enter needed. When stdin is not an interactive
console the keys degrade away and Ctrl+C still quits.
## v1.2.0

Watch mode added for the JavaScript target, supporting both Node and Deno

The syntax for this is slightly awkward:
`gleam run --target javascript -m vouch -- watch` noting that
the `--target` has to come before the `--` not after!

This controls the target of the parent watcher, and defaults the
inner runtime to that too. You can have the runtime of
the inner tests be different by specifying `--target=erlang` after
the `--`.

On the javascript runner, you can re-run all manually with `a` and
quitting will happen on `q`. On the erlang runner you have to press `q`
and then hit `<enter>` sorry, I can't figure out how to get more responsive
console in erlang. PRs welcome!

## v1.1.0

Expand Down
2 changes: 1 addition & 1 deletion examples/playground/manifest.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
packages = [
{ name = "argv", version = "1.1.0", build_tools = ["gleam"], requirements = [], otp_app = "argv", source = "hex", outer_checksum = "3277D100448BDB4A29B6D58C0F36F631CBC349E8BDD09766C6309DF202831140" },
{ name = "gleam_stdlib", version = "1.0.5", build_tools = ["gleam"], requirements = [], otp_app = "gleam_stdlib", source = "hex", outer_checksum = "CEE5B6C076A85B45F60C585F4316C63EC8B7127C119D5738C3958A9C4D50404E" },
{ name = "vouch", version = "1.1.0", build_tools = ["gleam"], requirements = ["argv", "gleam_stdlib"], source = "local", path = "../.." },
{ name = "vouch", version = "1.2.0", build_tools = ["gleam"], requirements = ["argv", "gleam_stdlib"], source = "local", path = "../.." },
]

[requirements]
Expand Down
2 changes: 1 addition & 1 deletion gleam.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
name = "vouch"
version = "1.1.0"
version = "1.2.0"
description = "A gleeunit-compatible test runner with todo outcomes, JSONL, teamcity and JUnit output, and process isolation"
licences = ["Apache-2.0"]
# Verified floor (podman, v1.14.0 images, both targets): the assert keyword
Expand Down
Loading