Skip to content

Tell a build of master from the 2.5.0 release: master moves on to 2.6.0-SNAPSHOT - #444

Merged
ssegura merged 1 commit into
masterfrom
chore/2.6.0-snapshot
Nov 10, 2026
Merged

ssegura merged 1 commit into
masterfrom
chore/2.6.0-snapshot

Conversation

@ssegura

@ssegura ssegura commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

Related: None. This is the step after the 2.5.0 release, the last of docs/ci.md's release steps.

What you can do now that you could not before

Tell a build of master from the release. v2.5.0 is tagged and published, and its modules are on Maven Central. From here on, a build of master says RESTest 2.6.0-SNAPSHOT in restest version and in every report.json, so a report produced by code that came after 2.5.0 is never taken for one produced by 2.5.0 itself.

Try it yourself

git clone --quiet -b chore/2.6.0-snapshot https://github.com/isa-group/RESTest.git restest-snapshot && cd restest-snapshot
./mvnw -q install -DskipTests
./restest version
grep -h '"\$id"' schemas/*.json

Real output, from a fresh clone of this branch on 10 November (the Java line is your own):

RESTest 2.6.0-SNAPSHOT
Java 25.0.4.1 (Eclipse Adoptium), Mac OS X 27.0.1 aarch64
  "$id": "https://raw.githubusercontent.com/isa-group/RESTest/v2.6.0/schemas/dictionary.schema.json",
  "$id": "https://raw.githubusercontent.com/isa-group/RESTest/v2.6.0/schemas/campaign.schema.json",

How it works

The version lives in the build files, and the tool reads it from there. -SNAPSHOT is how Maven writes "on the way to this version, not yet published". The tag v2.5.0 keeps the commit that says 2.5.0; master moves on to the next version and drops the -SNAPSHOT again when that one is released.

The JSON Schemas of a dictionary and a plan name the release they describe in their $id, the address each is published at. On master that is the release being prepared, v2.6.0, which PublishedSchemasTest requires to be no older than the snapshot.

What changed in the code

No Java code and no page changed.

  • The ten pom.xml, from 2.5.0 to 2.6.0-SNAPSHOT, with ./mvnw versions:set.
  • schemas/campaign.schema.json and schemas/dictionary.schema.json: $id from …/v2.5.0/… to …/v2.6.0/….

Evidence

  • Tests: ./mvnw clean install green on this branch: 4,981 tests, 0 failures, BUILD SUCCESS in 2 min 37 s. Among them are the 76 tests of PublishedSchemasTest. On CI's first attempt two rows failed, each in a test this pull request does not touch, and both were re-run:

    • Java 26 on ubuntu-latest, in EngineFaultsTest.a_redirection_nowhere_is_a_wait_for_a_connection, which follows a redirection to a port that accepts the connection and never answers, with a read timeout of 300 ms, and expects a wait for a connection: it got a wait for a reply, the timeout having run out in a part of the exchange the engine counts as the reply.
    • Java 25 on macos-latest, in FuzzingFindsWhatNominalMissesTest.the_awkward_values_are_what_find_it, which expects the empty search term among the awkward values of a run of 1,200 requests: with seed 1749106978450864122, its 120 awkward values did not include it, though the test's comment says that size reaches it every time.

    Both depend on timing or chance, as RunLoopTest.an_operation_told_to_wait_is_skipped did in Release 2.5.0: jbang, a skill for coding agents, and the documentation at one address #442; they are put right in a pull request of their own.

  • Architecture tests: unchanged, none weakened.

  • Mutation score: not touched.

  • Per-request overhead: not touched.

  • Smoke run: not touched.

  • Idle time: not touched.

  • Artefact: the installation of 2.5.0 was tried from outside on 10 November, as the README gives it, with no one signed in to GitHub, to the registry or to Maven Central:

    • Homebrew: publishing the release started homebrew.yml, and all six of its jobs are green. It wrote restest 2.5.0 into isa-group/homebrew-tap, with the checksum checksums_sha256.txt gives restest-2.5.0.tgz, and installed it from there on macOS and on Linux, 628 MB and 824 MB as chapter 2 of the manual says. brew install isa-group/tap/restest on a Mac with neither the tap nor RESTest installed it too, with an openjdk@21 of its own, and restest version printed RESTest 2.5.0 on Java 21.0.13.0.3 (Homebrew).
    • jbang: publishing the release started jbang.yml, and all six of its jobs are green. The catalog names es.us.isa.restest:restest-cli:2.5.0, and jbang --fresh restest@https://isa-group.github.io/jbang-catalog/jbang-catalog.json version, with a jbang folder of its own, printed RESTest 2.5.0. Its check jobs count 38 to 39 MB of libraries on Linux and macOS and 37 on Windows, what they counted on 1 November when chapter 2 was written, so its 37 MB stay.
    • The image: ghcr.io/isa-group/restest:2.5.0, pulled with an empty Docker configuration, printed RESTest 2.5.0 on Java 21.0.13. Chapter 2's restest script, written into a HOME of its own, ran a run against nothing that ended with 3 and left report.json and report.html in the folder, owned by the user. The registry gives :latest the same digest, sha256:3e72646c….
    • The archive: restest-2.5.0.tgz and checksums_sha256.txt, downloaded with curl. shasum -a 256 -c answered OK, restest version printed RESTest 2.5.0, and skills/restest/SKILL.md is in it.
    • The source: git clone --branch v2.5.0, with no credential helper, followed by ./mvnw -q install -DskipTests printed RESTest 2.5.0.
    • Maven Central: https://repo1.maven.org/maven2/es/us/isa/restest/restest-cli/2.5.0/ answers, and all 128 files of the eight modules are there. A project that depends on es.us.isa.restest:restest-cli:2.5.0, resolved from Central into an empty local repository, got 71 jars, the same names and the same bytes as the release archive's lib/, and restest version run from them printed RESTest 2.5.0.
    • The documentation site: publishing the release started documentation-site.yml, and all three of its jobs are green. https://isa-group.github.io/restest-site/llms.txt now names 2.5.0, and the page for coding agents the README sends an agent to answers.

Decisions taken

  • 2.6.0, not 2.5.1: the next release is meant to add features, which semantic versioning makes a minor version.
  • No release step changes. All eight of docs/ci.md's steps worked for 2.5.0 as they are written, including the first publication of the jbang catalog for a release and the documentation site's move to it, so neither that page nor an ADR is touched.

Open questions

None.


  • Targets master
  • English throughout, including comments and test names
  • The hard rules in AGENTS.md hold
  • Nothing from "Out of scope" in docs/DESIGN.md without explicit approval

🤖 Generated with Claude Code

….0-SNAPSHOT

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ssegura
ssegura merged commit b85ac74 into master Nov 10, 2026
31 of 33 checks passed
@ssegura
ssegura deleted the chore/2.6.0-snapshot branch November 10, 2026 18:48
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