build(deps-dev): bump org.assertj:assertj-core from 3.27.3 to 3.27.7 in /scripts/release-smoke/s8-core-render-docx - #514
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
added
dependencies
|
Superseded by #517, which does the same bump across all eight smoke setups rather than one, and closes the reason this arrived here. This PR targets The bump itself is right — assertj 3.27.7 is what the engine already uses. It just needs to reach all eight projects, which are deliberately identical consumers. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
…em to develop (#517) Dependabot opened #514 against main. That is the divergence the maven block's target-branch exists to prevent: main is the release pointer, moved by fast-forwarding develop onto it, and a commit landing on main directly ends that. The cause is scope — scripts/release-smoke sits outside every directory the block lists, so updates for those poms arrived through the default branch instead. The directory list now covers them. #514 also bumped one project of eight. The smoke setups are deliberately identical consumers, differing only in which artifacts they depend on, so a version moving in one of them is drift rather than an upgrade. All eight go to 3.27.7 together, which is the version the engine itself already uses. Verified by running the smoke against the published 2.1.1 train: 8/8 pass.
1 participant
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.