Repository navigation
Move master to 2.2.0-SNAPSHOT - #397
Merged
Merged
Conversation
The next version is 2.2.0: the shipped plan's shares changed, a dictionary has one shape, the plan format is at version 2, and the JSON Schemas' `$id`s, two decision records and the release workflow's example already name it. Every `pom.xml` said 2.1.1-SNAPSHOT, which nothing would have caught until the release pull request, since the schemas' test asks only that their version be no older than the build's. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
11 tasks done
ssegura
enabled auto-merge (squash)
October 14, 2026 17:13
ssegura
added a commit
that referenced
this pull request
Oct 14, 2026
**Related:** None ## What you can do now that you could not before A release no longer carries an empty `restest-idl` jar, and the repository no longer lists a module for the IDL language, inter-parameter dependencies, that nothing reads yet. The known limitations now say plainly that dependencies between parameters are not read, which a user of RESTest 1.x will look for. ## Try it yourself ```bash git fetch && git switch chore/idl-module-out-of-the-reactor ./mvnw -q package -DskipTests dist/assemble.sh target/dist > /dev/null && ls target/dist/restest-*/lib | grep '^restest-' ``` Real output: ``` restest-cli-2.1.1-SNAPSHOT.jar restest-core-2.1.1-SNAPSHOT.jar restest-exec-2.1.1-SNAPSHOT.jar restest-gen-2.1.1-SNAPSHOT.jar restest-oracles-2.1.1-SNAPSHOT.jar restest-report-2.1.1-SNAPSHOT.jar restest-spec-2.1.1-SNAPSHOT.jar restest-store-2.1.1-SNAPSHOT.jar ``` On `master` the list also has `restest-idl-2.1.1-SNAPSHOT.jar`, whose only class is `module-info.class`. ## How it works RESTest is built from modules that may only depend inwards, towards `restest-core`. One of them, `restest-idl`, was created at the start to hold the IDL language and a constraint solver, and has held nothing else since. It was still compiled, packaged, copied into every release and listed among what the tool is made of. It leaves the build until the first code that reads IDL arrives. The rule that checks the dependencies between modules keeps a place for it, so it comes back exactly where ADR-0004 put it, checked from its first class. ## What changed in the code - Removed: `restest-idl/` and the dependencies of `restest-gen`, `restest-cli` and `restest-arch-tests` on it; the two `requires io.restest.idl` in `module-info.java`. - `ArchitectureRules`: unchanged, with a comment on why the `Idl` layer stays. - `AGENTS.md`, `docs/DESIGN.md`, `docs/ci.md`, the root and arch-tests `pom.xml` comments: eight production modules. - ADR-0004 and ADR-0010 amended, and the index; `docs/known-limitations.md` says dependencies between parameters are not read. ## Evidence - [x] Tests: none added; `./mvnw verify` green locally. CI: this pull request's checks. - [x] Architecture tests: unchanged, none weakened; the layered rule keeps its `Idl` layer. - [x] Mutation score: not applicable. - [x] Per-request overhead: not applicable. - [x] Smoke run, two containerised APIs: the smoke job of this pull request. - [x] Idle time: not applicable. - [x] Artefact: the list above. ## Decisions taken - **The module leaves; the rule's layer stays.** Removing the layer would have been a change to an architecture test for no gain, and keeping it means nothing has to be decided again when IDL arrives. - **`AGENTS.md` changes** because it lists the modules; ADR-0030 says such a change is made in a pull request, and this is one. - **Order of merging.** #391, which runs the command-line tests three at a time, edits the same paragraph of `docs/ci.md`, and #397, which moves to 2.2.0-SNAPSHOT, changes `restest-idl/pom.xml`; whichever is merged second keeps the eight modules and deletes the file. ## Open questions None. --- - [x] Targets `master` - [x] English throughout, including comments and test names - [x] The hard rules in `AGENTS.md` hold - [x] Nothing from "Out of scope" in `docs/DESIGN.md` without explicit approval 🤖 Generated with [Claude Code](https://claude.com/claude-code)
… rather than moving to 2.2.0-SNAPSHOT Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
What you can do now that you could not before
A build of
mastersays it is 2.2.0-SNAPSHOT, the version being prepared, inrestest versionand inevery
report.jsonit writes.Try it yourself
git fetch && git switch chore/2.2.0-snapshot ./mvnw -q install -DskipTests dist/version.sh ./restest versionReal output:
On
masterboth say 2.1.1-SNAPSHOT.How it works
Since 2.1.0 the plan RESTest carries has new shares, a dictionary has one shape and the plan's format
is at version 2; the last two refuse files 2.1 read. That is a minor version, as the release notes of
2.2.0 will say, and the JSON Schemas'
$ids, two decision records and the release workflow's examplealready name 2.2.0. Every
pom.xmlstill said 2.1.1-SNAPSHOT. Nothing would have caught it until thepull request that prepares the release: the schemas' test only asks that their version be no older
than the build's.
What changed in the code
The
<version>of the tenpom.xmlfiles. Nothing else.Evidence
./mvnw verifygreen locally. CI: this pull request's checks.PublishedSchemasTestholds the schemas'$idsagainst the new version.
Decisions taken
pom.xml, out of the build;masterhas been merged into this branch since, so the ten that remain move to 2.2.0-SNAPSHOT.Open questions
None.
masterAGENTS.mdholddocs/DESIGN.mdwithout explicit approval🤖 Generated with Claude Code