build: align develop AssertJ test dependency to 3.27.7 #11

2026-10-02T01:56:59Z

KofTwentyTwo commented

2026-10-02 01:56:59 +00:00

(Migrated from github.com)

The develop candidate still explicitly pinned AssertJ 3.27.3 even though the older dependency proposal targets main. Update only the test dependency to 3.27.7, preserving revision, parent, CI and production source. This is the develop counterpart to #5; merging this PR does not satisfy #5's separate main-line obligation.

Validation: full mvn clean verify passed 52 tests, zero failures/errors/skips on exact develop base 9994a06af612f03269d4bc1d0cc83ad543e3ccf2. Dependency tree and test classpaths confirm AssertJ 3.27.7 and Byte Buddy 1.18.3 remain test-scoped. Main independently reviewed the complete one-pin diff and patch/POM hashes before signing and push.

Tracks QRun-IO/qqq#921. No release version bump, tag or publisher was run locally; normal develop-merge snapshot behavior remains unchanged.

The develop candidate still explicitly pinned AssertJ 3.27.3 even though the older dependency proposal targets main. Update only the test dependency to 3.27.7, preserving revision, parent, CI and production source. This is the develop counterpart to #5; merging this PR does not satisfy #5's separate main-line obligation. Validation: full `mvn clean verify` passed **52 tests, zero failures/errors/skips** on exact develop base `9994a06af612f03269d4bc1d0cc83ad543e3ccf2`. Dependency tree and test classpaths confirm AssertJ 3.27.7 and Byte Buddy 1.18.3 remain test-scoped. Main independently reviewed the complete one-pin diff and patch/POM hashes before signing and push. Tracks QRun-IO/qqq#921. No release version bump, tag or publisher was run locally; normal develop-merge snapshot behavior remains unchanged.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-workflows#11