Repository navigation
Release 1.1.0 - #141
Merged
Merged
Release 1.1.0#141
Conversation
The fixture retried only RuntimeExceptions, so an AssertionError from 'redis-cli --cluster create' (a node refusing connections) failed the test on the first attempt. Startup failures now retry on fresh ports and carry the tail of every node's redis.log.
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 the 1.1.0 release. This adds the Oracle Database store (#137, merged in #138). It is a compatible minor release: core, the PostgreSQL, Redis and in-memory stores, and their storage formats are unchanged, so upgrading from 1.0.x only needs the version bump.
Changes
ThreadmillVersion.CURRENT→1.1.0.1.1.0. Also removed the stale "unreleased 1.0.0 candidate" wording.CHANGELOG.md: the Unreleased section becomes1.1.0 — 2026-10-07, with entries for the Oracle store, its migration runner, Spring auto-configuration and the new contract case. Re-date it if the tag goes out on a different day.docs/compatibility.md: new "Upgrade from 1.0.0" section; it no longer describes 1.0.0 as unpublished.docs/RELEASING.md/docs/release-checklist.md: the release now has twelve published modules (addsthreadmill-store-oracle). The checklist gate command usesv<version>instead of a hard-codedv1.0.0.12ab7b0: the Redis failover test setup retried only onRuntimeException. AnAssertionErrorfromredis-cli --cluster createtherefore failed the test on its first attempt. This happened twice on 2026-10-07 (the PR #137 Add Oracle Database 19c+ store (threadmill-store-oracle) #138 run and themainrun foraad2eef). Setup failures now retry on fresh ports and include each node'sredis.logtail. This matters for the release because the tag-triggered release workflow runs the same tests, so a flake would fail the tag and use up the version number.Verification
./gradlew productionCheck verifyReleaseTag -PreleaseTag=v1.1.0 -PdependencyScanRequired=truepassed locally from clean outputs: every subproject check, real-store tests (including Oracle 23ai), soak regression, correctness and nudge simulations, Javadoc,dependencySecurityScan, example andartifactInspection.RedisFailoverTestpassed locally after the fixture change.Still open before tagging
docs/release-checklist.mdrequires running the Oracle suite against a real 19c database and recording the server release, because no free 19c image exists. CI only covers 23ai Free and 21c XE with the 19c optimizer setting. An 8-hour Oracle endurance run on 23ai passed (results in #137 Add Oracle Database 19c+ store (threadmill-store-oracle) #138).v1.1.0publishes all twelve modules to Maven Central automatically (publishingType = AUTOMATIC), and that cannot be undone. After merging, followdocs/RELEASING.md→ Tag and publish.