Bump org.assertj:assertj-core from 3.27.3 to 3.27.7 in /framework.tck - #478
Merged
cziegeler merged 1 commit intoMar 12, 2026
Conversation
Bumps [org.assertj:assertj-core](https://github.com/assertj/assertj) from 3.27.3 to 3.27.7. - [Release notes](https://github.com/assertj/assertj/releases) - [Commits](assertj/assertj@assertj-build-3.27.3...assertj-build-3.27.7) --- updated-dependencies: - dependency-name: org.assertj:assertj-core dependency-version: 3.27.7 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
deleted the
dependabot/maven/framework.tck/org.assertj-assertj-core-3.27.7
branch
March 12, 2026 14:23
paulrutter
added a commit
that referenced
this pull request
Aug 29, 2026
… the TCK
With the assertj range corrected the bndrun resolves, but the TCK then failed to
start assertj-core:
Unable to resolve assertj-core [8](R 8.0): missing requirement
osgi.wiring.package; (&(osgi.wiring.package=net.bytebuddy)
(version>=1.18.0)(!(version>=2.0.0)))
assertj-core 3.27.7 imports net.bytebuddy [1.18.0,2.0.0), but the TCK still pinned
byte-buddy 1.17.5. The dependency was bumped from 3.27.3 to 3.27.7 in #478 without
byte-buddy following, which is the same omission that left the bndrun requiring
assertj [3.27.3,3.27.4). Move byte-buddy to 1.18.12 in both the pom and the bndrun.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
paulrutter
added a commit
that referenced
this pull request
Aug 29, 2026
The OSGi Core TCK currently cannot resolve on any JDK, so framework.tck fails before executing a single test. That is what hid the FilterImpl defects fixed in this branch, and it also means CI cannot demonstrate the fix without repairing it. Two ranges were left behind when assertj-core was bumped from 3.27.3 to 3.27.7 in #478: - tck.bndrun still required assertj-core [3.27.3,3.27.4), so the bndrun could not be resolved at all: "assertj-core;version=[3.27.3,3.27.4) Not found in [... assertj-core;version=3.27.7 ...]". - assertj-core 3.27.7 imports net.bytebuddy [1.18.0,2.0.0) but byte-buddy was pinned at 1.17.5, so assertj-core then failed to start with an unresolved osgi.wiring.package requirement. Also removes a duplicate junit-platform-launcher dependency, which Maven reports as a malformed model and warns it may reject in future. Co-Authored-By: Claude Opus 4.8 <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.
Bumps org.assertj:assertj-core from 3.27.3 to 3.27.7.
Release notes
Sourced from org.assertj:assertj-core's releases.
... (truncated)
Commits
e840716[maven-release-plugin] prepare release assertj-build-3.27.785ca7ebDeprecateXmlStringPrettyFormatter77081dcMerge commit from forkb68fc24Bump github/codeql-action from 4.31.9 to 4.31.10 in the github-actions group ...0cf5bb6Bumpkotlin.versionfrom 2.1.0 to 2.2.21d393ef1Abort tests when symbolic links cannot be created (#3788)2212433Add IntelliJ custom inspection for test class names5717d02Update JetBrains icona8ec20bAdd icon for JetBrains productsc05fb3dBump Maven to 3.9.12 and Wrapper to 3.3.4Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.