Skip to content

deps(deps): bump the maven-minor-patch group across 1 directory with 6 updates - #57

Open
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/maven/develop/maven-minor-patch-94dd998885
Open

deps(deps): bump the maven-minor-patch group across 1 directory with 6 updates#57
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/maven/develop/maven-minor-patch-94dd998885

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 7, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the maven-minor-patch group with 6 updates in the / directory:

Package From To
org.junit:junit-bom 6.1.2 6.1.3
io.github.demchaav:graph-compose 2.1.1 2.3.0
io.github.demchaav:graph-compose-fonts 1.0.0 1.1.0
org.apache.maven.plugins:maven-compiler-plugin 3.15.0 3.16.0
org.apache.maven.plugins:maven-surefire-plugin 3.5.6 3.6.0
org.apache.maven:apache-maven 3.9.12 3.9.16

Updates org.junit:junit-bom from 6.1.2 to 6.1.3

Release notes

Sourced from org.junit:junit-bom's releases.

JUnit 6.1.3 = Platform 6.1.3 + Jupiter 6.1.3 + Vintage 6.1.3

See Release Notes.

Full Changelog: junit-team/junit-framework@r6.1.2...r6.1.3

Commits
  • f59f60d Release 6.1.3
  • cd8ec92 Finalize 6.1.3 release notes
  • c8729f2 Restore compatibility with GraalVM 25 (#5901)
  • ddc9e74 Update graalvm/setup-graalvm action to v1.6.4 (#5959)
  • fe2c52a Update plugin org.graalvm.buildtools.native to v1.1.7 (#5923)
  • 62afc02 Delay GraalVM plugin updates for 3 days
  • 0cc2902 Skip graalVmTest task if GraalVM env vars are not set
  • f6bbfc5 Move GraalVM tests to separate test task (#5903)
  • e87e052 Update plugin org.graalvm.buildtools.native to v1.1.6 (#5899)
  • 1cd56df Update plugin org.graalvm.buildtools.native to v1.1.5 (#5880)
  • Additional commits viewable in compare view

Updates io.github.demchaav:graph-compose from 2.1.1 to 2.3.0

Release notes

Sourced from io.github.demchaav:graph-compose's releases.

GraphCompose v2.3.0

v2.3.0 — 2026-08-31

Public API

  • A header or footer can name its font family. DocumentHeaderFooter.fontName(...) picks the family the zone is typeset in; the PDF and PPTX backends resolve it through the document's own font library, the same way body text is resolved. Until now a zone was drawn in standard-14 Helvetica and nothing else, so a footer outside WinAnsi — a Cyrillic page counter, a Greek imprint — came out as a row of ?. The default is still FontName.HELVETICA and resolves to the same standard-14 face the zone drew before, so an existing header or footer renders unchanged down to its placement. Naming a family is the whole mechanism: there is no automatic fallback here any more than there is in the body, so a code point the chosen family cannot encode is still substituted with ?.

  • DOCX exports a page zone as a real Word footer. The zone the PDF and PPTX backends draw is now written into a w:ftr / w:hdr part, which is the first header/footer support the DOCX exporter has had. The band's children become runs on one Word line: a paragraph contributes its runs, a flex spacer becomes the right tab stop. Page numbers are the part that could not simply be copied over — a semantic export hands the node tree to Word and Word paginates, so a number written as text would be right on one page and wrong on the rest. PageContext.pageNumber() and pageTotal() return a node instead of an int: resolved text on a fixed-layout export, a live PAGE / NUMPAGES field in Word. The same zone definition therefore serves both lanes, and the field's placeholder run carries the node's text style, so a styled page number stays styled in Word rather than snapping to the document default. Reading PageContext.number() on a semantic export raises UnsupportedOperationException naming the alternative rather than returning a plausible lie. Node kinds outside the mapped set are skipped and reported. A page predicate (appliesTo) is fixed-layout capability — there is no page to test it against when the definition is written — so a zone that carries one is exported to every page, and the export logs what it could not honor.

  • A page zone draws a node subtree instead of text slots. DocumentPageZone, registered through document.chrome().zone(...), takes a content function called once per page with that page's PageContext and returns any DocumentNode. The subtree is laid out against a canvas the size of the band and spliced into the compiled layout graph, so every fixed-layout backend draws it with no code of its own: a badge, a link annotation, an image, a shape, a table, right-to-left text and any font the document has all work in a zone because it is the body's machinery, not a second copy of it. Page numbers come from the context — page.number() + " / " + page.total() — so the band needs no placeholder tokens, and anything the tokens could not express (roman numerals, an offset, a different line on the last page) is ordinary Java in the same lambda. A page reference inside a zone resolves against the body's anchors, so a footer can say "appendix on page N" about content it does not itself contain. appliesTo(page -> ...) decides which pages carry the zone, which separates "is this page numbered" from "is the band drawn" — the two that DocumentPageNumbering conflates. The predicate decides painting only: a reserving zone's band comes out of every page's content area either way, so hiding the zone on the cover does not reflow the cover. A zone reserves its height by default and does not paginate: content that needs more than the band raises

... (truncated)

Changelog

Sourced from io.github.demchaav:graph-compose's changelog.

v2.3.0 — 2026-08-31

Public API

  • A header or footer can name its font family. DocumentHeaderFooter.fontName(...) picks the family the zone is typeset in; the PDF and PPTX backends resolve it through the document's own font library, the same way body text is resolved. Until now a zone was drawn in standard-14 Helvetica and nothing else, so a footer outside WinAnsi — a Cyrillic page counter, a Greek imprint — came out as a row of ?. The default is still FontName.HELVETICA and resolves to the same standard-14 face the zone drew before, so an existing header or footer renders unchanged down to its placement. Naming a family is the whole mechanism: there is no automatic fallback here any more than there is in the body, so a code point the chosen family cannot encode is still substituted with ?.

  • DOCX exports a page zone as a real Word footer. The zone the PDF and PPTX backends draw is now written into a w:ftr / w:hdr part, which is the first header/footer support the DOCX exporter has had. The band's children become runs on one Word line: a paragraph contributes its runs, a flex spacer becomes the right tab stop. Page numbers are the part that could not simply be copied over — a semantic export hands the node tree to Word and Word paginates, so a number written as text would be right on one page and wrong on the rest. PageContext.pageNumber() and pageTotal() return a node instead of an int: resolved text on a fixed-layout export, a live PAGE / NUMPAGES field in Word. The same zone definition therefore serves both lanes, and the field's placeholder run carries the node's text style, so a styled page number stays styled in Word rather than snapping to the document default. Reading PageContext.number() on a semantic export raises UnsupportedOperationException naming the alternative rather than returning a plausible lie. Node kinds outside the mapped set are skipped and reported. A page predicate (appliesTo) is fixed-layout capability — there is no page to test it against when the definition is written — so a zone that carries one is exported to every page, and the export logs what it could not honor.

  • A page zone draws a node subtree instead of text slots. DocumentPageZone, registered through document.chrome().zone(...), takes a content function called once per page with that page's PageContext and returns any DocumentNode. The subtree is laid out against a canvas the size of the band and spliced into the compiled layout graph, so every fixed-layout backend draws it with no code of its own: a badge, a link annotation, an image, a shape, a table, right-to-left text and any font the document has all work in a zone because it is the body's machinery, not a second copy of it. Page numbers come from the context — page.number() + " / " + page.total() — so the band needs no placeholder tokens, and anything the tokens could not express (roman numerals, an offset, a different line on the last page) is ordinary Java in the same lambda. A page reference inside a zone resolves against the body's anchors, so a footer can say "appendix on page N" about content it does not itself contain. appliesTo(page -> ...) decides which pages carry the zone, which separates "is this page numbered" from "is the band drawn" — the two that DocumentPageNumbering conflates. The predicate decides painting only: a reserving zone's band comes out of every page's content area either way, so hiding the zone on the cover does not reflow the cover. A zone reserves its height by default and does not paginate: content that needs more than the band raises AtomicNodeTooLargeException naming the zone and its height rather than being dropped —

... (truncated)

Commits
  • 62afc02 Release v2.3.0
  • c41dc0f docs: pre-release fixes — stage the 2.3 roadmap line and the status prose
  • 874679f Merge remote-tracking branch 'origin/chore/knowledge-pack' into release/2.3
  • cd4ea57 Merge remote-tracking branch 'origin/develop' into release/2.3
  • f288f92 ci: bump actions/setup-java from 5 to 6 in the github-actions group (#617)
  • dfe2b83 docs(examples): showcase the rest of the chrome surface
  • ba9cacd docs(recipes): account for every Java fence on the pages that make claims
  • 87312e0 feat(knowledge): prove the auto-column alignment trap, both sides of it
  • cfed87e feat(knowledge): resolve what backs each claim, and prove one that nothing did
  • 408b3ed chore(knowledge): fold the page-zone API into the surfaces
  • Additional commits viewable in compare view

Updates io.github.demchaav:graph-compose-fonts from 1.0.0 to 1.1.0

Release notes

Sourced from io.github.demchaav:graph-compose-fonts's releases.

GraphCompose v1.1.0

Highlights

  • compose-first built-in template usage is now the documented default
  • backend-neutral DocumentComposer and handler-driven rendering make the engine less PDF-centric internally
  • layout snapshot testing is now part of the regression workflow for pagination and geometry changes
  • runnable examples now cover CV, cover letter, invoice, proposal, and weekly schedule generation
  • document-level PDF features now include QR/barcodes, watermarks, headers/footers, bookmarks, metadata, protection, explicit page breaks, and dividers
  • visual showcase tests make pagination, document chrome, and barcode output easier to inspect
  • benchmark tooling now includes current-speed, comparative, and diffable JSON/CSV reports
  • an experimental live preview dev tool is available in test scope for fast template iteration

Added

  • barcode support with QR, Code 128, and EAN-13 builders
  • watermark support
  • configurable headers and footers with page numbers and separators
  • PDF bookmarks / outline generation
  • document metadata support
  • PDF protection hooks
  • explicit page-break and divider builders
  • visual showcase render tests
  • benchmark export and diff tooling
  • one-command benchmark runner

Compatibility

  • older tagged JitPack releases such as v1.0.3 remain usable
  • deprecated render(...) template adapters are still available for compatibility
  • new docs and examples now prefer compose(...)

v1.0.3 — First Public Release

Highlights:

  • Declarative document composition with reusable builders and layout systems
  • Automatic multi-page layout and pagination
  • Markdown support via Flexmark
  • Shared font registration and reusable text styles
  • Template layer with CvTheme and TemplateBuilder
  • JitPack distribution for easy integration
Changelog

Sourced from io.github.demchaav:graph-compose-fonts's changelog.

v1.1.0 - 2026-04-13

Highlights

  • shifted the public built-in template narrative to compose(DocumentSession, ...)
  • added document-level PDF features for richer real-world output
  • moved the engine further away from PDF-centric internals through backend-neutral composition and render-handler seams
  • strengthened architecture guard rails for template scene builders
  • expanded visual testing and benchmark tooling for day-to-day development

Added

  • canonical DocumentSession contract as the primary composition seam
  • layout snapshot extraction and JSON-based regression coverage for resolved document geometry
  • runnable examples/ module for CV, cover letter, invoice, proposal, and weekly schedule generation
  • new built-in business templates and data models for invoice, proposal, and weekly schedule documents
  • barcode support with QR, Code 128, and EAN-13 builders
  • watermark support
  • configurable headers and footers with page numbers and separators
  • PDF bookmarks / outline generation
  • document metadata support
  • PDF protection hooks
  • explicit page-break and divider builders
  • visual showcase render tests for barcodes, QR codes, pagination, and document chrome
  • current-speed benchmark suite
  • benchmark JSON/CSV export and diff tooling
  • one-command benchmark runner: scripts/run-benchmarks.ps1

Changed

  • bumped the library release to v1.1.0
  • updated README installation snippets to the new release version
  • documented built-in templates as compose-first by default
  • refreshed README visuals to show barcode/QR and compose-first template output
  • added release-facing notes for the experimental live preview dev tool in test scope
  • refreshed release documentation to point contributors at visual tests and benchmark workflows

Architecture and CI

  • engine-side text measurement and rendering dispatch are now more explicitly decoupled from PDFBox-specific implementation details
  • added template boundary guard coverage so *SceneBuilder classes stay free of backend-specific PDFBox types
  • split architecture/documentation guards into a dedicated CI job that can be required independently in branch protection

Compatibility notes

  • older tagged JitPack releases remain usable as long as consumers pin a specific version such as v1.0.3
  • deprecated render(...) template adapters remain available for compatibility, but new docs and examples now prefer compose(...)
Commits
  • cdedd9d Prepare v1.1.0 release
  • a5424fe Add quiet logging to stress and endurance benchmarks
  • dc65c2b Add benchmark diff workflow to README
  • 07b95b8 Add benchmark report export and usage docs
  • e9f7ef1 feat: Add PdfPageBreakRenderHandler and visual showcase tests
  • 2e08ecf feat: Add comprehensive document-level features and barcode support
  • ecefc8e Extract shared PDF template adapter support
  • 849103d Enforce template boundaries and compose-first examples
  • 3567aae Split built-in templates into compose-first scene builders
  • 4c6fa50 docs: Add contributor architecture rules for engine changes
  • Additional commits viewable in compare view

Updates org.apache.maven.plugins:maven-compiler-plugin from 3.15.0 to 3.16.0

Release notes

Sourced from org.apache.maven.plugins:maven-compiler-plugin's releases.

3.16.0

🚀 New features and improvements

🐛 Bug Fixes

📝 Documentation updates

👻 Maintenance

📦 Dependency updates

Commits
  • e7bba6e [maven-release-plugin] prepare release maven-compiler-plugin-3.16.0
  • c906809 Avoid using deprecated method CompilerConfiguration.setCompilerVersion
  • ad74fee Replace adopt-openj9 by semeru JDK distribution on GH
  • beb0eda Recompile when dependencies change (#1102)
  • a0b689e [MCOMPILER-578] Track outputs across compiler executions (#1091)
  • 2e81228 Fix incremental detection of empty sources, 3.x (#1075)
  • 2132f5b configure ATR project
  • 5992b77 Build fails when annotation processor list is empty (but present) (#1077)
  • acccef7 Bump plexusCompilerVersion from 2.16.2 to 2.17.0
  • 72bc445 Bump org.codehaus.plexus:plexus-java from 1.5.2 to 1.6.0
  • Additional commits viewable in compare view

Updates org.apache.maven.plugins:maven-surefire-plugin from 3.5.6 to 3.6.0

Release notes

Sourced from org.apache.maven.plugins:maven-surefire-plugin's releases.

3.6.0

Please refer to the main page for what's new https://maven.apache.org/surefire/ And the migration page https://maven.apache.org/surefire/maven-surefire-plugin/whats-new-3-6-0.html

🚀 New features and improvements

🐛 Bug Fixes

📝 Documentation updates

👻 Maintenance

... (truncated)

Commits
  • 0ff622b [maven-release-plugin] prepare release surefire-3.6.0
  • bb3932a Let's go for 3.6.0 release
  • 3002a16 Bump mavenVersion from 3.9.14 to 3.9.16
  • 61a531d Bump Maven parent version from 47 to 49 (#3449)
  • e52ead4 [SUREFIRE-523] Link all reported tests to source XRef (#3445)
  • 45102fa [SUREFIRE-3446] Fix direct selection of JUnit Jupiter @​Nested classes (#3447)
  • b2e1f70 Fix #3303: distinguish JUnit 6 ParameterizedClass invocations (#3432)
  • c051938 Discover tests in a fork when a toolchain JDK is used (#3444)
  • db75df8 Bump org.codehaus.plexus:plexus-java from 1.5.2 to 1.6.0 (#3441)
  • 77f2759 Bump org.codehaus.plexus:plexus-interpolation from 1.29 to 1.30.0
  • Additional commits viewable in compare view

Updates org.apache.maven:apache-maven from 3.9.12 to 3.9.16

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
deps(deps): bump the maven-minor-patch group across 1 directory with …
2ed7160 
…6 updates

Bumps the maven-minor-patch group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [org.junit:junit-bom](https://github.com/junit-team/junit-framework) | `6.1.2` | `6.1.3` |
| [io.github.demchaav:graph-compose](https://github.com/DemchaAV/GraphCompose) | `2.1.1` | `2.3.0` |
| [io.github.demchaav:graph-compose-fonts](https://github.com/DemchaAV/GraphCompose) | `1.0.0` | `1.1.0` |
| [org.apache.maven.plugins:maven-compiler-plugin](https://github.com/apache/maven-compiler-plugin) | `3.15.0` | `3.16.0` |
| [org.apache.maven.plugins:maven-surefire-plugin](https://github.com/apache/maven-surefire) | `3.5.6` | `3.6.0` |
| org.apache.maven:apache-maven | `3.9.12` | `3.9.16` |



Updates `org.junit:junit-bom` from 6.1.2 to 6.1.3
- [Release notes](https://github.com/junit-team/junit-framework/releases)
- [Commits](junit-team/junit-framework@r6.1.2...r6.1.3)

Updates `io.github.demchaav:graph-compose` from 2.1.1 to 2.3.0
- [Release notes](https://github.com/DemchaAV/GraphCompose/releases)
- [Changelog](https://github.com/DemchaAV/GraphCompose/blob/main/CHANGELOG.md)
- [Commits](DemchaAV/GraphCompose@v2.1.1...v2.3.0)

Updates `io.github.demchaav:graph-compose-fonts` from 1.0.0 to 1.1.0
- [Release notes](https://github.com/DemchaAV/GraphCompose/releases)
- [Changelog](https://github.com/DemchaAV/GraphCompose/blob/main/CHANGELOG.md)
- [Commits](DemchaAV/GraphCompose@v1.0.0...v1.1.0)

Updates `org.apache.maven.plugins:maven-compiler-plugin` from 3.15.0 to 3.16.0
- [Release notes](https://github.com/apache/maven-compiler-plugin/releases)
- [Commits](apache/maven-compiler-plugin@maven-compiler-plugin-3.15.0...maven-compiler-plugin-3.16.0)

Updates `org.apache.maven.plugins:maven-surefire-plugin` from 3.5.6 to 3.6.0
- [Release notes](https://github.com/apache/maven-surefire/releases)
- [Commits](apache/maven-surefire@surefire-3.5.6...surefire-3.6.0)

Updates `org.apache.maven:apache-maven` from 3.9.12 to 3.9.16

---
updated-dependencies:
- dependency-name: org.junit:junit-bom
  dependency-version: 6.1.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: io.github.demchaav:graph-compose
  dependency-version: 2.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: io.github.demchaav:graph-compose-fonts
  dependency-version: 1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-compiler-plugin
  dependency-version: 3.16.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-surefire-plugin
  dependency-version: 3.6.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven:apache-maven
  dependency-version: 3.9.16
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies, maven. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot
dependabot Bot requested a review from DemchaAV as a code owner September 7, 2026 23:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@DemchaAV DemchaAV Awaiting requested review from DemchaAV DemchaAV is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants