chore: bump async-test-lib to 1.7.0-RC8 - #361
Merged
Merged
Conversation
RC5 to RC8. Verified before pinning: the full suite (1464 tests, 4 @AsyncTest classes among them) ran green against the RC8 artifact from Maven Central on 2026-08-04. RC8 rejects invocations/threads below 1 at config build time, closing the hole where a misconfigured @AsyncTest reported a passing test whose body never ran. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UsCqogShCj1AVTEcP4FzLg
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
PIsberg
added a commit
that referenced
this pull request
Aug 4, 2026
…e async-test-lib clone (#363) docs/DEPENDENCIES.md is new: what each third-party artifact is for, split by what it costs a consumer. Three reach the consumer's annotation-processor path (jspecify, slf4j-api, logback-classic) and vibetags-annotations has none at all; the rest is test or build scope and never leaves this repository. It names the parent property holding each version rather than restating the number, and records the versions deliberately skipped so the next sweep does not re-derive that slf4j 2.1.0-alpha1, maven-compiler-plugin 4.0.0-beta-4, surefire 3.6.0-M1 and jar/source 4.0.0-beta-1 are prereleases. Bumps, all stable, checked against maven-metadata.xml on repo1.maven.org rather than a changelog: ArchUnit 1.4.2 -> 1.5.0, SnakeYAML 2.5 -> 2.6, shade 3.5.2 -> 3.6.2, exec 3.2.0 -> 3.6.3, spotbugs 4.10.2.0 -> 4.10.3.0, pitest-maven 1.25.8 -> 1.25.9, pitest-junit5 1.2.2 -> 1.2.3, cyclonedx 2.9.2 -> 2.9.3. Two defects turned up while inventorying. vibetags-annotations/build.gradle was analysed by PMD 7.24.0 while the parent and vibetags/build.gradle were on 7.26.0, so the two modules ran different rule sets and a rule added between those releases applied to one of them. The existing parity check reads dependency coordinates, and Gradle's PMD version is a toolVersion assignment, so nothing saw it. BuildVersionParityTest now checks it; confirmed red on 7.24.0 before the fix. Four CI jobs cloned github.com/PIsberg/async-test-lib at v1.7.0-RC5 and ran `mvn install` on it before every build, on the strength of a comment saying the artifact is not on Maven Central. It is, and has been: 1.7.0-RC8 resolves from Central into an empty local repository (verified with -Dmaven.repo.local pointing at a fresh directory). The clone tag had also been left at RC5 when the dependency moved to RC8 in #361, so the step was installing a version nothing asked for, and one of those clones failed transiently today and turned an unrelated PR red. Removed, and the stale comments in vibetags/pom.xml and vibetags/build.gradle corrected. async-test-lib stays at 1.7.0-RC8. The 1.7.0 that versions:display-dependency-updates offers exists only as a local install and 404s on Central. Also: llms.txt claimed "all 39 annotations" against the 44 that exist. Fixed by dropping the restated count, which is the rule the rest of the docs follow, so there is nothing left to drift. Verified: full Maven build 1465 tests green, both Gradle builds green. Claude-Session: https://claude.ai/code/session_01MokCW5bBivp1snfzhTjajo Co-authored-by: Claude Opus 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
1 participant
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.
RC5 to RC8, ahead of the upcoming 1.7.0 release.
Why now: RC8 rejects invocations/threads below 1 at @AsyncTest config build time, closing the hole where a misconfigured test reported green without ever running its body. This suite's 4 @AsyncTest classes are exactly the consumers that hole endangered.
Verified before the pin moved: the full suite (1464 tests, 0 failures) ran green against the RC8 artifact downloaded from Maven Central on 2026-08-04, on this branch's tree.
🤖 Generated with Claude Code
https://claude.ai/code/session_01UsCqogShCj1AVTEcP4FzLg