Repository navigation
Tell a build of master from the 2.5.0 release: master moves on to 2.6.0-SNAPSHOT - #444
Merged
Merged
Conversation
….0-SNAPSHOT Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
7 of 10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
masterfrom the release.v2.5.0is tagged and published, and its modules are on Maven Central. From here on, a build ofmastersaysRESTest 2.6.0-SNAPSHOTinrestest versionand in everyreport.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
Real output, from a fresh clone of this branch on 10 November (the Java line is your own):
How it works
The version lives in the build files, and the tool reads it from there.
-SNAPSHOTis how Maven writes "on the way to this version, not yet published". The tagv2.5.0keeps the commit that says 2.5.0;mastermoves on to the next version and drops the-SNAPSHOTagain 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. Onmasterthat is the release being prepared,v2.6.0, whichPublishedSchemasTestrequires to be no older than the snapshot.What changed in the code
No Java code and no page changed.
pom.xml, from2.5.0to2.6.0-SNAPSHOT, with./mvnw versions:set.schemas/campaign.schema.jsonandschemas/dictionary.schema.json:$idfrom…/v2.5.0/…to…/v2.6.0/….Evidence
Tests:
./mvnw clean installgreen on this branch: 4,981 tests, 0 failures, BUILD SUCCESS in 2 min 37 s. Among them are the 76 tests ofPublishedSchemasTest. On CI's first attempt two rows failed, each in a test this pull request does not touch, and both were re-run: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.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 seed1749106978450864122, 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_skippeddid 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.yml, and all six of its jobs are green. It wroterestest 2.5.0intoisa-group/homebrew-tap, with the checksumchecksums_sha256.txtgivesrestest-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/resteston a Mac with neither the tap nor RESTest installed it too, with anopenjdk@21of its own, andrestest versionprintedRESTest 2.5.0onJava 21.0.13.0.3 (Homebrew).jbang.yml, and all six of its jobs are green. The catalog nameses.us.isa.restest:restest-cli:2.5.0, andjbang --fresh restest@https://isa-group.github.io/jbang-catalog/jbang-catalog.json version, with a jbang folder of its own, printedRESTest 2.5.0. Itscheckjobs 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.ghcr.io/isa-group/restest:2.5.0, pulled with an empty Docker configuration, printedRESTest 2.5.0on Java 21.0.13. Chapter 2'srestestscript, written into aHOMEof its own, ran a run against nothing that ended with3and leftreport.jsonandreport.htmlin the folder, owned by the user. The registry gives:latestthe same digest,sha256:3e72646c….restest-2.5.0.tgzandchecksums_sha256.txt, downloaded withcurl.shasum -a 256 -cansweredOK,restest versionprintedRESTest 2.5.0, andskills/restest/SKILL.mdis in it.git clone --branch v2.5.0, with no credential helper, followed by./mvnw -q install -DskipTestsprintedRESTest 2.5.0.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 ones.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'slib/, andrestest versionrun from them printedRESTest 2.5.0.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
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.
masterAGENTS.mdholddocs/DESIGN.mdwithout explicit approval🤖 Generated with Claude Code