Repository navigation
chore(release): 1.14.2 - #1228
Merged
Merged
Conversation
Bumps every pin to 1.14.2 with bump-version.sh, including versions/pom.xml, which every build outside the reactor resolves; a stale pin there resolves the old release from Central and proves nothing about this build. Moves the japicmp baseline from 1.14.0 to 1.14.1, the release users upgrade off. Left on 1.14.0, the gate could not catch a break of anything 1.14.1 added. Corrects @SInCE on the API new since 1.14.1 that was tagged 1.14.1: the six kotlinx Mutex hooks, AsyncTestContext.kotlinMutexReentrancyDetector() and KotlinMutexReentrancyDetector (#1007). None of them existed at v1.14.1. Cuts the changelog, merges its two Added headings, and adds an Upgrading note: like 1.14.1, this patch carries what SUPPORT_POLICY calls minor (a new detector, detectors firing on missed cases, a discovery check that can redden a build), and the owner kept the patch number. SUPPORT_POLICY records the exception next to the 1.14.1 one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Prepares 1.14.2. Nothing is tagged: merging, then pushing
v1.14.2, are the owner's steps, and the tag triggers the Central publish.Why each change
bump-version.sh, includingversions/pom.xml. Every build outside the reactor resolves that pin; left on 1.14.1, they would resolve the old release from Central and pass without testing this build (SatelliteVersionsTest).@sincecorrected on API new since 1.14.1 that said1.14.1: the six kotlinxMutexhooks inAgentConcurrencyUtilHooks,AsyncTestContext.kotlinMutexReentrancyDetector()andKotlinMutexReentrancyDetector([P3] Kotlin coroutine model: runBlocking on a dispatcher, Mutex reentrancy, races across suspensions #1007). Found by checking each@since 1.14.1member against thev1.14.1tree; none of these eight existed there.[1.14.2] - 2026-11-08, its two### Addedheadings merged into one, and an Upgrading note added. Like 1.14.1, this patch carries whatSUPPORT_POLICY.mdcalls minor: a new detector (KOTLIN_MUTEX_REENTRANCY), detectors that now fire on missed cases ([P3] Parallel streams: only forEach is attributed, intermediate lambdas and reduce are not #1172, [P3] execute on a ThreadPoolExecutor: subclasses are unobserved and getQueue shows the wrapper #1173, [P3] Runtime.getRuntime().gc() is not woven, though ExplicitGcDetector says it detects it #1179, [P3] Flaky: corpus agent-pairs row agent_jctoolsHandOff_offererWritesAfterTheOffer silent once #1133), and a discovery check that can turn a build red ([P3] Discovery: class-level @AsyncTest templates that are private, static or non-void still run nothing #1149). The note also lists the two changes that remove findings ([P2] ATOMIC_NON_ATOMIC_UPDATE reports a get then set whose stored value does not depend on the read #1187, [P3] LivelockDetector: a body's own snapshots may read a correct hand-off as rapid state cycling #1180).SUPPORT_POLICY.mdrecords the 1.14.2 exception next to the 1.14.1 one: patch number kept by owner choice.Verification
mvn --batch-mode clean verify "-Dlicense.mock.mode=true"on JDK 26 in a clean worktree: BUILD SUCCESS in 15:47, 4,100 tests, 0 failures, 0 errors, 0 skipped, with checkstyle, PMD and SpotBugs bound toverify.check-published-artifact.sh 1.14.1 --fixfirst:~/.m2held local builds posing as the 1.14.1 lib, agent and analysis jars, which were moved aside and re-fetched from Central with SHA-1 checked. japicmp then comparedasync-test-lib-1.14.2.jaragainst that Central 1.14.1 jar: no changes.Docs touched:
docs/CHANGELOG.md,docs/SUPPORT_POLICY.md, and the version strings inREADME.md,docs/QUICK_REFERENCE.md,docs/DISTRIBUTION.mdand.claude/SKILL.md. No follow-up work is left out of scope.🤖 Generated with Claude Code