Skip to content

chore(deps): bump the maven-minor-patch group across 1 directory with 16 updates - #21

Closed
dependabot[bot] wants to merge 88 commits into
mainfrom
dependabot/maven/maven-minor-patch-553cac1d39
Closed

dependabot[bot] wants to merge 88 commits into
mainfrom
dependabot/maven/maven-minor-patch-553cac1d39

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

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

Package From To
run.endive:runtime 1.0.1 1.1.0
run.endive:wasm 1.0.1 1.1.0
run.endive:wasi 1.0.1 1.1.0
run.endive:compiler 1.0.1 1.1.0
run.endive:wasm 1.0.1 1.1.0
run.endive:wasi 1.0.1 1.1.0
run.endive:compiler 1.0.1 1.1.0
com.fasterxml.jackson.core:jackson-databind 2.22.1 2.22.2
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.plugins:maven-failsafe-plugin 3.5.6 3.6.0
org.apache.maven.plugins:maven-jar-plugin 3.5.0 3.5.1
org.codehaus.mojo:flatten-maven-plugin 1.7.3 1.8.0
org.codehaus.mojo:exec-maven-plugin 3.6.3 3.6.4
org.apache.maven.plugin-tools:maven-plugin-annotations 3.15.2 3.16.0
org.apache.maven.plugins:maven-plugin-plugin 3.15.2 3.16.0
org.apache.maven.plugins:maven-failsafe-plugin 3.5.6 3.6.0
org.apache.maven.plugins:maven-antrun-plugin 3.1.0 3.2.0
org.apache.maven:apache-maven 3.9.9 3.9.16
org.apache.maven.wrapper:maven-wrapper 3.2.0 3.3.4

Updates run.endive:runtime from 1.0.1 to 1.1.0

Release notes

Sourced from run.endive:runtime's releases.

1.1.0

What's Changed

... (truncated)

Commits
  • 91d41f8 Release version update 1.1.0
  • 2a555b8 Add the Endive 1.1.0 release blog post (#179)
  • 4cbb6c2 Shorten the method names documentation (#180)
  • d0cc4f4 Allow configuring a method prefixer in the build-time compiler (#178)
  • dab3cf8 chore(deps): bump com.diffplug.spotless:spotless-maven-plugin from 3.9.0 to 3...
  • 59a879a Document the experimental Redline native compiler (#166)
  • 82781c0 feat: optionally use WASM function names for compiled methods (#168)
  • 6dd5f8f chore(deps): bump org.apache.maven.plugins:maven-compiler-plugin (#177)
  • 5ebc2ae chore(deps): bump com.puppycrawl.tools:checkstyle from 14.0.0 to 14.1.0 (#176)
  • eb7417d Create imports through a factory that picks native or bytecode (#174)
  • Additional commits viewable in compare view

Updates run.endive:wasm from 1.0.1 to 1.1.0

Release notes

Sourced from run.endive:wasm's releases.

1.1.0

What's Changed

... (truncated)

Commits
  • 91d41f8 Release version update 1.1.0
  • 2a555b8 Add the Endive 1.1.0 release blog post (#179)
  • 4cbb6c2 Shorten the method names documentation (#180)
  • d0cc4f4 Allow configuring a method prefixer in the build-time compiler (#178)
  • dab3cf8 chore(deps): bump com.diffplug.spotless:spotless-maven-plugin from 3.9.0 to 3...
  • 59a879a Document the experimental Redline native compiler (#166)
  • 82781c0 feat: optionally use WASM function names for compiled methods (#168)
  • 6dd5f8f chore(deps): bump org.apache.maven.plugins:maven-compiler-plugin (#177)
  • 5ebc2ae chore(deps): bump com.puppycrawl.tools:checkstyle from 14.0.0 to 14.1.0 (#176)
  • eb7417d Create imports through a factory that picks native or bytecode (#174)
  • Additional commits viewable in compare view

Updates run.endive:wasi from 1.0.1 to 1.1.0

Release notes

Sourced from run.endive:wasi's releases.

1.1.0

What's Changed

... (truncated)

Commits
  • 91d41f8 Release version update 1.1.0
  • 2a555b8 Add the Endive 1.1.0 release blog post (#179)
  • 4cbb6c2 Shorten the method names documentation (#180)
  • d0cc4f4 Allow configuring a method prefixer in the build-time compiler (#178)
  • dab3cf8 chore(deps): bump com.diffplug.spotless:spotless-maven-plugin from 3.9.0 to 3...
  • 59a879a Document the experimental Redline native compiler (#166)
  • 82781c0 feat: optionally use WASM function names for compiled methods (#168)
  • 6dd5f8f chore(deps): bump org.apache.maven.plugins:maven-compiler-plugin (#177)
  • 5ebc2ae chore(deps): bump com.puppycrawl.tools:checkstyle from 14.0.0 to 14.1.0 (#176)
  • eb7417d Create imports through a factory that picks native or bytecode (#174)
  • Additional commits viewable in compare view

Updates run.endive:compiler from 1.0.1 to 1.1.0

Release notes

Sourced from run.endive:compiler's releases.

1.1.0

What's Changed

... (truncated)

Commits
  • 91d41f8 Release version update 1.1.0
  • 2a555b8 Add the Endive 1.1.0 release blog post (#179)
  • 4cbb6c2 Shorten the method names documentation (#180)
  • d0cc4f4 Allow configuring a method prefixer in the build-time compiler (#178)
  • dab3cf8 chore(deps): bump com.diffplug.spotless:spotless-maven-plugin from 3.9.0 to 3...
  • 59a879a Document the experimental Redline native compiler (#166)
  • 82781c0 feat: optionally use WASM function names for compiled methods (#168)
  • 6dd5f8f chore(deps): bump org.apache.maven.plugins:maven-compiler-plugin (#177)
  • 5ebc2ae chore(deps): bump com.puppycrawl.tools:checkstyle from 14.0.0 to 14.1.0 (#176)
  • eb7417d Create imports through a factory that picks native or bytecode (#174)
  • Additional commits viewable in compare view

Updates run.endive:wasm from 1.0.1 to 1.1.0

Release notes

Sourced from run.endive:wasm's releases.

1.1.0

What's Changed

dependabot Bot and others added 30 commits June 27, 2026 23:17
Bumps the maven-minor-patch group with 22 updates:

| Package | From | To |
| --- | --- | --- |
| [com.dylibso.chicory:runtime](https://github.com/dylibso/chicory) | `1.7.3` | `1.7.5` |
| [com.dylibso.chicory:wasm](https://github.com/dylibso/chicory) | `1.7.3` | `1.7.5` |
| [com.dylibso.chicory:wasi](https://github.com/dylibso/chicory) | `1.7.3` | `1.7.5` |
| [com.dylibso.chicory:compiler](https://github.com/dylibso/chicory) | `1.7.3` | `1.7.5` |
| [com.fasterxml.jackson.core:jackson-databind](https://github.com/FasterXML/jackson) | `2.15.2` | `2.22.0` |
| [org.apache.maven.plugins:maven-compiler-plugin](https://github.com/apache/maven-compiler-plugin) | `3.12.1` | `3.15.0` |
| [org.apache.maven.plugins:maven-surefire-plugin](https://github.com/apache/maven-surefire) | `3.2.5` | `3.5.6` |
| [org.apache.maven.plugins:maven-failsafe-plugin](https://github.com/apache/maven-surefire) | `3.2.5` | `3.5.6` |
| [org.apache.maven.plugins:maven-jar-plugin](https://github.com/apache/maven-jar-plugin) | `3.3.0` | `3.5.0` |
| [org.apache.maven.plugins:maven-source-plugin](https://github.com/apache/maven-source-plugin) | `3.3.0` | `3.4.0` |
| [org.apache.maven.plugins:maven-javadoc-plugin](https://github.com/apache/maven-javadoc-plugin) | `3.6.3` | `3.12.0` |
| [org.codehaus.mojo:flatten-maven-plugin](https://github.com/mojohaus/flatten-maven-plugin) | `1.6.0` | `1.7.3` |
| [org.apache.maven.plugins:maven-gpg-plugin](https://github.com/apache/maven-gpg-plugin) | `3.1.0` | `3.2.8` |
| [org.codehaus.mojo:exec-maven-plugin](https://github.com/mojohaus/exec-maven-plugin) | `3.1.0` | `3.6.3` |
| [org.apache.maven.plugins:maven-shade-plugin](https://github.com/apache/maven-shade-plugin) | `3.5.1` | `3.6.2` |
| [info.picocli:picocli](https://github.com/remkop/picocli) | `4.7.5` | `4.7.7` |
| [info.picocli:picocli-codegen](https://github.com/remkop/picocli) | `4.7.5` | `4.7.7` |
| [org.apache.maven:maven-plugin-api](https://github.com/apache/maven) | `3.8.1` | `3.9.16` |
| [org.apache.maven.plugin-tools:maven-plugin-annotations](https://github.com/apache/maven-plugin-tools) | `3.6.4` | `3.15.2` |
| org.apache.maven:maven-core | `3.8.1` | `3.9.16` |
| org.apache.maven.plugin-testing:maven-plugin-testing-harness | `3.3.0` | `3.5.1` |
| [org.apache.maven.plugins:maven-invoker-plugin](https://github.com/apache/maven-invoker-plugin) | `3.2.2` | `3.10.1` |


Updates `com.dylibso.chicory:runtime` from 1.7.3 to 1.7.5
- [Release notes](https://github.com/dylibso/chicory/releases)
- [Commits](dylibso/chicory@1.7.3...1.7.5)

Updates `com.dylibso.chicory:wasm` from 1.7.3 to 1.7.5
- [Release notes](https://github.com/dylibso/chicory/releases)
- [Commits](dylibso/chicory@1.7.3...1.7.5)

Updates `com.dylibso.chicory:wasi` from 1.7.3 to 1.7.5
- [Release notes](https://github.com/dylibso/chicory/releases)
- [Commits](dylibso/chicory@1.7.3...1.7.5)

Updates `com.dylibso.chicory:compiler` from 1.7.3 to 1.7.5
- [Release notes](https://github.com/dylibso/chicory/releases)
- [Commits](dylibso/chicory@1.7.3...1.7.5)

Updates `com.dylibso.chicory:wasm` from 1.7.3 to 1.7.5
- [Release notes](https://github.com/dylibso/chicory/releases)
- [Commits](dylibso/chicory@1.7.3...1.7.5)

Updates `com.dylibso.chicory:wasi` from 1.7.3 to 1.7.5
- [Release notes](https://github.com/dylibso/chicory/releases)
- [Commits](dylibso/chicory@1.7.3...1.7.5)

Updates `com.dylibso.chicory:compiler` from 1.7.3 to 1.7.5
- [Release notes](https://github.com/dylibso/chicory/releases)
- [Commits](dylibso/chicory@1.7.3...1.7.5)

Updates `com.fasterxml.jackson.core:jackson-databind` from 2.15.2 to 2.22.0
- [Commits](https://github.com/FasterXML/jackson/commits)

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

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

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

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

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

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

Updates `org.codehaus.mojo:flatten-maven-plugin` from 1.6.0 to 1.7.3
- [Release notes](https://github.com/mojohaus/flatten-maven-plugin/releases)
- [Commits](mojohaus/flatten-maven-plugin@1.6.0...1.7.3)

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

Updates `org.codehaus.mojo:exec-maven-plugin` from 3.1.0 to 3.6.3
- [Release notes](https://github.com/mojohaus/exec-maven-plugin/releases)
- [Commits](mojohaus/exec-maven-plugin@exec-maven-plugin-3.1.0...3.6.3)

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

Updates `info.picocli:picocli` from 4.7.5 to 4.7.7
- [Release notes](https://github.com/remkop/picocli/releases)
- [Changelog](https://github.com/remkop/picocli/blob/main/RELEASE-NOTES.md)
- [Commits](remkop/picocli@v4.7.5...v4.7.7)

Updates `info.picocli:picocli-codegen` from 4.7.5 to 4.7.7
- [Release notes](https://github.com/remkop/picocli/releases)
- [Changelog](https://github.com/remkop/picocli/blob/main/RELEASE-NOTES.md)
- [Commits](remkop/picocli@v4.7.5...v4.7.7)

Updates `org.apache.maven:maven-plugin-api` from 3.8.1 to 3.9.16
- [Release notes](https://github.com/apache/maven/releases)
- [Commits](apache/maven@maven-3.8.1...maven-3.9.16)

Updates `org.apache.maven.plugin-tools:maven-plugin-annotations` from 3.6.4 to 3.15.2
- [Release notes](https://github.com/apache/maven-plugin-tools/releases)
- [Commits](apache/maven-plugin-tools@maven-plugin-tools-3.6.4...maven-plugin-tools-3.15.2)

Updates `org.apache.maven:maven-core` from 3.8.1 to 3.9.16

Updates `org.apache.maven.plugin-testing:maven-plugin-testing-harness` from 3.3.0 to 3.5.1

Updates `info.picocli:picocli-codegen` from 4.7.5 to 4.7.7
- [Release notes](https://github.com/remkop/picocli/releases)
- [Changelog](https://github.com/remkop/picocli/blob/main/RELEASE-NOTES.md)
- [Commits](remkop/picocli@v4.7.5...v4.7.7)

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

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

---
updated-dependencies:
- dependency-name: com.dylibso.chicory:runtime
  dependency-version: 1.7.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: com.dylibso.chicory:wasm
  dependency-version: 1.7.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: com.dylibso.chicory:wasi
  dependency-version: 1.7.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: com.dylibso.chicory:compiler
  dependency-version: 1.7.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: com.dylibso.chicory:wasm
  dependency-version: 1.7.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: com.dylibso.chicory:wasi
  dependency-version: 1.7.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: com.dylibso.chicory:compiler
  dependency-version: 1.7.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: com.fasterxml.jackson.core:jackson-databind
  dependency-version: 2.22.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.15.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-surefire-plugin
  dependency-version: 3.5.6
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-failsafe-plugin
  dependency-version: 3.5.6
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-jar-plugin
  dependency-version: 3.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-source-plugin
  dependency-version: 3.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-javadoc-plugin
  dependency-version: 3.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.codehaus.mojo:flatten-maven-plugin
  dependency-version: 1.7.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-gpg-plugin
  dependency-version: 3.2.8
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.codehaus.mojo:exec-maven-plugin
  dependency-version: 3.6.3
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-shade-plugin
  dependency-version: 3.6.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: info.picocli:picocli
  dependency-version: 4.7.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: info.picocli:picocli-codegen
  dependency-version: 4.7.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven:maven-plugin-api
  dependency-version: 3.9.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugin-tools:maven-plugin-annotations
  dependency-version: 3.15.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven:maven-core
  dependency-version: 3.9.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugin-testing:maven-plugin-testing-harness
  dependency-version: 3.5.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: info.picocli:picocli-codegen
  dependency-version: 4.7.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-invoker-plugin
  dependency-version: 3.10.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-failsafe-plugin
  dependency-version: 3.5.6
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps the actions group with 5 updates:

| Package | From | To |
| --- | --- | --- |
| [actions/checkout](https://github.com/actions/checkout) | `4` | `7` |
| [actions/setup-java](https://github.com/actions/setup-java) | `4` | `5` |
| [actions/cache](https://github.com/actions/cache) | `4` | `6` |
| [actions/upload-artifact](https://github.com/actions/upload-artifact) | `4` | `7` |
| [softprops/action-gh-release](https://github.com/softprops/action-gh-release) | `2` | `3` |


Updates `actions/checkout` from 4 to 7
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v4...v7)

Updates `actions/setup-java` from 4 to 5
- [Release notes](https://github.com/actions/setup-java/releases)
- [Commits](actions/setup-java@v4...v5)

Updates `actions/cache` from 4 to 6
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@v4...v6)

Updates `actions/upload-artifact` from 4 to 7
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](actions/upload-artifact@v4...v7)

Updates `softprops/action-gh-release` from 2 to 3
- [Release notes](https://github.com/softprops/action-gh-release/releases)
- [Changelog](https://github.com/softprops/action-gh-release/blob/master/CHANGELOG.md)
- [Commits](softprops/action-gh-release@v2...v3)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: actions/setup-java
  dependency-version: '5'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: actions/cache
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: actions/upload-artifact
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: softprops/action-gh-release
  dependency-version: '3'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
These majors require dedicated migrations (Java baseline / breaking APIs) and
currently fail CI; ignore them so Dependabot stops reopening failing PRs.
Chicory has been donated to the Bytecode Alliance and renamed to Endive.
Rename the chicory4j-provider module to endive4j-provider, the
provider/engine id "chicory" to "endive", and ChicoryConfig/ChicoryConfigs
to EndiveConfig/EndiveConfigs. Switch the dependency from
com.dylibso.chicory to run.endive 1.0.0 (packages com.dylibso.chicory.* ->
run.endive.*).

BREAKING CHANGE: the provider/engine id "chicory" is now "endive" and the
ChicoryConfig/ChicoryConfigs facades are now EndiveConfig/EndiveConfigs.
…omponent instantiation

Previously WasmtimeComponentAdapter.instantiate enabled WASI Preview 2 with an
empty context (dropping the caller's WasiContext) and ignored ComponentConfig
entirely, so a component could be granted no preopens/env and no resource
limits via the high-level API.

- Translate WasiContext -> WasiPreview2Config (preopens [host==guest], env,
  stdio inherit); network denied by default (deny-by-default; not yet
  expressible via WasiContext).
- Apply ComponentConfig limits: StoreLimits (memory/table/instances) at store
  creation + fuel/epoch when the engine has them enabled.
- Create the store per instantiation (so limits apply) and close stores with
  the component; loadComponent no longer pre-creates a shared store.
- Override instantiate(ComponentConfig) and instantiate(LinkingContext,
  ComponentConfig).

Unit-tested (WasmtimeComponentAdapterWasiTest): env/stdio/preopens forwarded,
empty context is deny-all + network-denied. Follow-ons: granular guest-path /
per-dir permissions on WasiContext, and an end-to-end WASI-using-component test.
…nstance.invoke

ComponentInstance.invoke's javadoc promises a natural Java<->WIT type mapping and
return values already arrived as natural Java, but arguments were passed straight
to the native layer, which requires WitValue instances ("Argument 0 must be a
WitValue instance, got java.lang.String").

WasmtimeComponentInstanceAdapter.invoke now marshals each Java arg via toWitValue:
Boolean->bool, Byte/Short/Integer/Long->s8/s16/s32/s64, Float/Double->f32/f64,
Character->char, String->string, byte[]->list<u8>, non-empty homogeneous List->list
(recursive). A WitValue passes through unchanged (escape hatch for option/result/
record/variant/enum/flags and exact unsigned/narrow integer widths); null and empty
lists raise a clear UnsupportedFeatureException naming the arg index + function
instead of a cryptic native error.

Unit-tested (WasmtimeComponentInstanceMarshalTest, 4 cases).
With the shared component engine now fuel-metered (wasmtime4j Fix 11), a store
created on a fuel-enabled engine defaults to 0 fuel and the component traps on its
first instruction. newStore now sets the store's fuel whenever the engine meters
fuel: the ComponentConfig.fuelLimit cap when present, else MAX_VALUE (unlimited).
This is the value the native layer reads as the per-instance compute cap.
…tantiation

doInstantiate now passes ComponentConfig.maxMemoryBytes and epochDeadline to the
native instantiation via ComponentLinker.setComponentResourceLimits (-1 = unlimited).
The component runs on wasmtime4j's shared component engine (metered for fuel + epoch),
so these apply regardless of this engine's own config. Completes ComponentConfig
resource-limit forwarding (fuel + memory + epoch).
WasiContext gains readOnlyPreopenDirs() and DefaultWasiContext.builder().preopenDir(dir,
writable); toWasiPreview2Config maps a read-only grant to DirPerms.readOnly()/
FilePerms.readOnly() instead of full perms. The native layer already honored per-dir
permission bits, so a read-only preopen now actually denies guest writes (was a Java-only
gap). preopenDir(dir) still defaults to read-write — existing callers are unchanged.
WasiContext.preopenGuestPaths() + DefaultWasiContext.preopenDir(hostDir, guestPath, writable); toWasiPreview2Config forwards the guest path (native preopen already accepted one). A preopen can now expose a host dir at a different guest path without leaking the host layout. Default stays host==guest.
…nfig path

The no-arg enableWasiPreview2() leaves JniComponentLinker.wasiConfig null,
so instantiate() falls back to nativeInstantiateWithLinker — currently a
stub that returns a phantom instance ID without registering the instance
in the component engine's HashMap. The subsequent invoke then fails with
"Instance ID N not found in engine".

Always pass a WasiPreview2Config (an empty default when the caller
provides no WasiContext) so wasiConfig gets set and instantiate() routes
through nativeInstantiateComponentWithWasi, which actually registers the
instance. Deny-by-default: an empty config grants no preopens, no env,
no network.
The api-level invoke() returns natural Java shapes (Map for records,
List for tuples/lists, Optional for options, etc.) via WitValue.toJava()
in the wasmtime provider. This is asymmetric with the argument side
(records/variants must be built as WitValue) and drops WIT-specific
typing on the way back (u64 width, enum discriminant vs case name,
option's inner type).

Add invokeWit as an optional typed variant that returns the provider's
WitValue tree instead. Default delegates to invoke and only round-trips
cleanly for providers that already return WitValue there. Wasmtime
provider overrides to call the new wasmtime4j ComponentInstance.invokeWit
directly, skipping the toJava() unwrap on the return path. Shared arg
marshalling extracted into marshalArgs so invoke and invokeWit can't
drift in what they accept.
Components with WIT imports beyond WASI previously required consumers to
unwrap the api Component down to the native wasmtime4j ComponentLinker
and call defineFunction directly — defeating the api abstraction and
coupling call sites to wasmtime4j-jni.

Adds:
- WitHostFunction (Object[] args -> Object[] results)
- WitHostFunctionDefinition (witPath + fn)
- LinkingContext.witHostFunctions()
- DefaultLinkingContext.Builder.addWitHostFunction(witPath, fn)

Wasmtime provider wraps each WitHostFunction in a native ComponentHostFunction
and calls ComponentLinker.defineFunction(witPath, impl) before instantiation.
The Object[] elements are the provider's native WIT value type — for wasmtime
that is ComponentVal — since a cross-provider WIT value abstraction is out of
scope here. Host functions written against a specific provider stay
portable-within-provider; cross-provider portability at this layer waits for
a future WitValue-style abstraction.
Bumps wasmtime4j to 46.0.1-1.2.0 and cuts the 2.1.0 release covering
end-to-end Component Model invocation on the Wasmtime provider, WIT-typed
host imports, WASI preopen enhancements, and per-instance component
resource caps.
… 14 updates (#12)

---
updated-dependencies:
- dependency-name: run.endive:runtime
  dependency-version: 1.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: run.endive:wasm
  dependency-version: 1.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: run.endive:wasi
  dependency-version: 1.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: run.endive:compiler
  dependency-version: 1.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: run.endive:wasm
  dependency-version: 1.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: run.endive:wasi
  dependency-version: 1.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: run.endive:compiler
  dependency-version: 1.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: org.graalvm.polyglot:polyglot
  dependency-version: 24.2.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: org.graalvm.polyglot:wasm-community
  dependency-version: 24.2.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: org.graalvm.polyglot:wasm-community
  dependency-version: 24.2.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: com.fasterxml.jackson.core:jackson-databind
  dependency-version: 2.22.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: org.junit.jupiter:junit-jupiter
  dependency-version: 5.14.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.junit.jupiter:junit-jupiter-api
  dependency-version: 5.14.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.junit.jupiter:junit-jupiter-params
  dependency-version: 5.14.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.junit.jupiter:junit-jupiter-api
  dependency-version: 5.14.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.junit.jupiter:junit-jupiter-params
  dependency-version: 5.14.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.springframework.boot:spring-boot-autoconfigure
  dependency-version: 3.5.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.springframework.boot:spring-boot-actuator-autoconfigure
  dependency-version: 3.5.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.springframework.boot:spring-boot-configuration-processor
  dependency-version: 3.5.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.springframework.boot:spring-boot-starter-test
  dependency-version: 3.5.16
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.springframework.boot:spring-boot-actuator-autoconfigure
  dependency-version: 3.5.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.springframework.boot:spring-boot-configuration-processor
  dependency-version: 3.5.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.springframework.boot:spring-boot-starter-test
  dependency-version: 3.5.16
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…cement

Add a provider-agnostic egress capability so a policy can grant outbound network access to
specific endpoints. NetworkEgressRule (literal IP or CIDR + port + tcp/udp) with total,
fail-closed matching incl. CIDR containment. WasiContext gains allowNetwork() (default false)
+ egressRules() (default empty = deny-all); DefaultWasiContext.Builder gains allowNetwork() +
allowEgress().

WasmtimeComponentAdapter.toWasiPreview2Config maps a granted context to allowNetwork(true) +
allowTcp/allowUdp + a SocketAddrCheck that permits ONLY connect/outgoing-datagram to an
allow-listed endpoint and denies every bind/listen use (egress only, no ingress). The native
wasmtime4j machinery (allowNetwork/socketAddrCheck) already existed; this is the Java plumbing.

Version 2.1.0 -> 2.2.0-SNAPSHOT (needs a Maven Central publish for a real release).
Cuts the 2.2.0 release covering a Wasmtime network egress allow-list
(fail-closed CIDR/port/protocol matching, egress-only via SocketAddrCheck),
plus a wasmtime4j bump to 46.0.1-1.3.0 and the maven-minor-patch group
Dependabot roll-up (endive 1.0.1, GraalVM 24.2.2, JUnit 5.14.4, Jackson
2.22.1, Spring Boot 3.5.16).
…hrough

Add ai.tegmentum.webassembly4j.api.FsAccessObserver, an engine-neutral,
observe-only callback fired when a component's path-based filesystem open
is denied on the WASI-preopen path (java.lang types only; no runtime dep).
Surface it as an optional WasiContext.fsAccessObserver().

In the wasmtime provider, toWasiPreview2Config now bridges a present
observer to wasmtime4j's WasiPreview2Config.fsAccessObserver so a denied
component open-at/stat-at surfaces the raw guest path + classified reason
to the host. Observe-only: it cannot change the enforcement outcome.

Requires a wasmtime4j build carrying the FsAccessObserver hook; against a
runtime without it the observer is simply never invoked.
The fs-denial passthrough in the wasmtime provider calls
WasiPreview2Config.fsAccessObserver, which ships in wasmtime4j 46.0.1-1.3.1
(FsAccessObserver hook). Bump the dependency so the passthrough compiles against
the released observer.
Cuts the 2.3.0 release covering the engine-neutral FsAccessObserver
(observe-only callback fired when a component's path-based filesystem
open is denied on the WASI preopen path, surfacing raw guest path +
classified reason) with a wasmtime provider passthrough to
wasmtime4j's WasiPreview2Config.fsAccessObserver, plus a wasmtime4j
bump to 46.0.1-1.3.1 carrying the underlying hook.
…iNnConfig)

Introduces a provider-neutral WasiNnConfig marker in webassembly4j-api and
threads it through LinkingContext (default null) so a caller can opt a
component into wasi:nn without touching the native ComponentLinker. The
wasmtime4j-provider translates it to ai.tegmentum.wasmtime4j.wasi.nn.WasiNnConfig
and calls the native ComponentLinker#enableWasiNn(WasiNnConfig) added in
wasmtime4j 46.0.1-1.4.0.

Providers without wasi:nn surface a WasmException from their native linker
which InstantiationException wraps at the api boundary.

Bumps wasmtime4j dep 46.0.1-1.3.1 -> 46.0.1-1.4.0 and cuts webassembly4j 2.4.0.
Closes a regression where plugins that call
DefaultLinkingContext.Builder#enableWasiNn(...) unconditionally against
the shipping 46.0.1-1.4.x wasmtime4j native (built without the wasi-nn
cargo feature) throw at instantiation time even for guests that import
zero wasi:nn interfaces.

- Adds a default-false supportsWasiNn() probe on both LinkingContext and
  Component so callers can gate the enable path on the actual provider
  capability, not on their own configuration intent.
- Overrides supportsWasiNn() on WasmtimeComponentAdapter to delegate
  (via reflection, so wasmtime4j-jni stays runtime-scoped) to
  JniComponentLinker.wasiNnAvailable(), which reports the compile-time
  wasi-nn feature bit of the loaded libwasmtime4j.
- Bumps webassembly4j 2.4.0 -> 2.4.1 (patch, additive API) and pins
  wasmtime4j 46.0.1-1.4.0 -> 46.0.1-1.4.2 to pick up the JNI probe.
…tion

Add a provider-neutral abstraction for the returned own<T> case:
WitCallableResource wraps a component-model resource handle with
invokeMethod/invokeMethodWit/close, so JVM plugins driving components
via SPARQL SERVICE can address aggregate-state, iterator, and
handle-then-method WIT patterns without threading the receiver +
instance pair by hand.

The wasmtime4j provider implements this by binding a wasmtime4j
WitResource to the ComponentInstance it came from and delegating
through the new invokeResourceMethodWit + dropResource entry points
added to wasmtime4j 46.0.1-1.4.5. Endive/graalwasm/wamr providers
inherit the default UnsupportedFeatureException — extending them is
a follow-up when their underlying runtimes grow equivalent hooks.

Bump wasmtime4j.version to 46.0.1-1.4.5 to pick up the new native +
Java surface.
…via counter component

Add the deferred half of Follow-up 2: a synthetic Rust component + JUnit
smoke test that drives WitCallableResource through the full lifecycle
against real wasmtime4j resource-method dispatch, replacing the
"honest failure" placeholder with observed behavior.

Rust component (src/test/rust/counter_component/):
- Exports the interface-scoped resource pattern from the task spec
  (tegmentum:test-counter/counter-api with a counter resource + ctor +
  increment + value methods) and additionally writes a lifecycle marker
  file from its constructor and Drop impl. The marker file is the
  primary drop-verification signal because Java's System.setErr swap
  does not redirect the WASI stderr path (writes go straight to FD 2),
  so a file-based signal is what actually survives the JVM/WASM
  boundary. Built via `cargo component build --release --target
  wasm32-wasip2`, wired into `mvn test` through exec-maven-plugin with a
  `-Dskip.rust.build` escape hatch.

Java smoke test (WasmtimeCallableResourceTest):
- resourceLifecycleAcrossInterfaceScopedMethods — invokeWit the
  interface-scoped [constructor]counter, asserts the returned own<T>
  surfaces as WitOwn, wraps via asCallableResource, runs
  invokeMethod(increment) x 3 + invokeMethod(value)==3, then verifies
  close() is idempotent.
- invokingAfterCloseThrows — post-close invokeMethod must throw.
- closeInvokesGuestSideDrop — verifies the guest's Drop impl actually
  ran by reading the marker file the guest wrote to a preopened dir
  (final value = 2 after two increments).

Provider adapter (WasmtimeComponentInstanceAdapter#asCallableResource):
- Broaden the input type from WitResource to also accept WitOwn /
  WitBorrow, translating via WitResource.fromHandle. The wasmtime WIT
  deserializer surfaces `own<T>` / `borrow<T>` as WitOwn / WitBorrow
  (discriminators 22/23), not WitResource — the prior check rejected
  the shape actually returned by invokeWit at run time. No change to
  the provider-neutral WitCallableResource surface itself.
Transitional helper on wasmtime4j-provider that lets JVM plugins
dispatch against SPARQL extension guests speaking either the new
sparql-extension ABI (tegmentum:webfunction@0.1.0) or the old flat
evaluate/aggregate-step/aggregate-finish ABI. Detects the guest's
shape once at construction and caches the result. Delete when every
guest in ~/git/webfunctions/crates/ exports the sparql-extension
world. See webfunction-wit/docs/design/bridging-dispatch.md.
Round-trip coverage for BridgingSparqlExtensionDispatch. Two fake
ComponentInstance implementations — one advertising the new-shape
extension@0.1.0#call / aggregate@0.1.0#new-aggregate exports, one
advertising only the old flat evaluate / aggregate-step /
aggregate-finish exports — dispatch through the same helper API and
assert identical caller-visible results. Also covers the shim
aggregate resource's step/finish routing, close idempotency, and the
generic bridge() fallback used by the Stardog overlay cardinality
export.
Adds a regression test to `BridgingSparqlExtensionDispatchTest` that
drives a real wasmtime component (the counter fixture already used by
`WasmtimeCallableResourceTest`) and asserts
`ComponentInstance.hasFunction` returns `true` for the
interface-qualified export
`tegmentum:test-counter/counter-api@0.1.0#[method]counter.value` and
for the interface-scoped constructor, plus a negative-control check
on a fake qualified name to ensure the fix isn't masking probes with
an unconditional `true`.

Before wasmtime4j 46.0.1-1.4.6 the probe returned `false` for every
interface-qualified name even when `invokeWit` of the same name
succeeded, which silently forced
`BridgingSparqlExtensionDispatch#filterIsNewShape` to fall back to
the old-shape ABI for new-shape guests at construction time. This
test would have caught the regression at CI time.

Bumps wasmtime4j.version to 46.0.1-1.4.6 to consume the fix.
… fallback

BridgingSparqlExtensionDispatch#aggregateIsNewShape used only
ComponentInstance#hasFunction("tegmentum:webfunction/aggregate@
0.1.0#new-aggregate") for shape detection. On wasmtime4j runtimes
older than 46.0.1-1.4.6 (the majority of downstream plugin builds)
the probe returned false for interface-qualified export names, so
new-shape guests mis-detected as old-shape and dispatch trapped
against absent flat aggregate-step exports. Plugins worked around
the same issue for filter dispatch via a plugin-side
instance.exportsInterface(...) check but had no equivalent for
aggregate.

Fix hoists the fallback into the bridging helper: shape detection
now returns true when either the qualified export probe or the
containing interface probe succeeds. Also:

- unwrap the new-aggregate ctor's WitResult<aggregate-state, string>
  ok-arm before asCallableResource (WitOwn/WitBorrow expected)
- wrap the returned resource so callers can dispatch step/finish
  via the neutral method vocabulary the ShimAggregateResource
  already accepts (wasmtime resource-method dispatch wants the
  fully qualified [method]aggregate-state.<name> path)

Bumps webassembly4j to 2.4.2.
…erface

Adds two default methods to webassembly4j-api's ComponentInstance so
providers can surface the wasmtime4j 1.4.7 fuel accessors:

- consumeFuel(long amount): default throws UnsupportedFeatureException.
  The wasmtime4j-provider overrides to delegate to the underlying
  wasmtime4j ComponentInstance's consumeFuel.
- fuelConsumed(): default returns -1 (unsupported sentinel). The
  wasmtime4j-provider overrides to delegate to fuelConsumed.

Providers whose engine is not fuel-metered (endive, graalwasm, wamr,
wasm3) inherit the defaults — no changes.

Test: WasmtimeComponentFuelAccountingTest covers the three key
behaviours on a real fuel-metered component instance built from the
existing counter_component:
- consumeFuel(K) then fuelConsumed() returns K
- consumeFuel beyond remaining throws + leaves store fuel unchanged
- a real guest invocation shows non-zero fuelConsumed afterwards

Bumps webassembly4j to 2.4.3 and pins wasmtime4j.version to 46.0.1-1.4.7.

Closes the upstream gap that forced the stardog-plugin Phase 1 fuel-
metering Java-side counter workaround.
Zachary Whitley and others added 25 commits July 26, 2026 12:49
The api-layer Table contract (webassembly4j-api) promises
IndexOutOfBoundsException from get(int) and set(int, Object) when
index >= size(). The underlying ai.tegmentum.wasmtime4j.jni.JniTable
implementation surfaces out-of-bounds access as a bare RuntimeException
wrapping a WasmRuntimeException, and negative indices come out as
IllegalArgumentException (Validation.requireNonNegative).

Neither shape matches the contract, so the adapter now bounds-checks the
index against nativeTable.getSize() before delegating; failures raise
IndexOutOfBoundsException with a descriptive message. The delegating
call itself is unchanged.

Fixes the getOutOfBoundsThrows / setOutOfBoundsThrows cases in
WasmtimeTableAdapterTest introduced by the preceding commit.
…mportDefinition

WasmtimeLinkingContextExternImportsTest exercises:

  - api-layer builder collects all four typed variants; ordering preserved
  - api-layer accepts a pre-built ExternImportDefinition via addExternImport
  - default LinkingContext.externImports() is empty
  - end-to-end MemoryImport wired on the module's own native store; host
    write is observable from the guest via the exported load_i32
  - end-to-end TableImport wired on the same store; instantiate succeeds
    and the api-layer table size flows through
  - end-to-end GlobalImport wired on the same store; guest bump is
    observable on the host handle and vice versa
  - FunctionImport raises UnsupportedOperationException with the variant
    kind and (moduleName, name) coordinates in the message
  - MemoryImport with a memory that unwrap-fails raises LinkingException
    naming the (moduleName, name) pair and identifying the cause

The three end-to-end tests reach through the package-private
WasmtimeModuleAdapter.store() accessor to construct WasmMemory / WasmTable
/ WasmGlobal on the module's own native store — the wasmtime constraint is
that extern imports must live on the same Store as the module being
instantiated. That accessor already existed; no adapter API change is
needed for these tests.

Note: bump in IMPORT_GLOBAL_MODULE is 0-arg to sidestep a pre-existing
i32-in/void-out fast-path shortcut in WasmtimeFunctionAdapter (out of scope
for this charter).

Refs: f-webassembly4j-linkingcontext-imports-wiring-fix-charter-2026-07-26
…close)

Closes r.1 of the F-Webassembly4j-Table-Interface-Completion charter.

Interface (webassembly4j-api):
  - Adds default-throwing OptionalInt maxSize(), Object get(int),
    void set(int, Object), int grow(int, Object) to Table.
  - Default bodies throw UnsupportedOperationException so wamr4j-provider,
    graalwasm4j-provider, wasm3-provider, endive4j-provider remain
    compile-clean without modification.
  - Interface-level Javadoc documents the try/catch escape and points
    to EngineCapabilities as the coarser probe.

Implementation (wasmtime4j-provider):
  - WasmtimeTableAdapter overrides all four methods, delegating to
    ai.tegmentum.wasmtime4j.WasmTable.
  - maxSize maps native -1 (unbounded) to OptionalInt.empty().
  - get/set bounds-check locally so the native JniTable RuntimeException
    (out-of-bounds) and IllegalArgumentException (negative) are both
    normalized to the api-contract IndexOutOfBoundsException.

Tests (wasmtime4j-provider):
  - WasmtimeTableAdapterTest covers all four operations plus baseline
    size and IOOBE contract (9 tests, all pass on JNI backend).

Verification: mvn -B -pl webassembly4j-api,wasmtime4j-provider -am
-Dskip.rust.build=true -Dtest='!JavaToWasmRoundTripTest,!WasmtimeCallableResourceTest'
-DfailIfNoTests=false test => BUILD SUCCESS (162 api + 78 provider tests).

Deferred (charter): fill/copy/init/dropElementSegment/growAsync,
elementType(), the Ref abstraction, release cut, CHANGELOG update.
…i-arc

Function was the sole api-layer type lacking unwrap(Class<T>). All other
types (Table, Memory, Global, Engine, Instance) already provide it as the
provider-escape hatch for capabilities not surfaced at the api layer.

Default in interface returns Optional.empty(). WasmtimeFunctionAdapter
implements to return the underlying ai.tegmentum.wasmtime4j.WasmFunction.

Disciplined per operator gate: parity across api-layer types; applies to
any consumer needing funcref extraction for Table.set or dynamic dispatch
scenarios (JIT loaders, plugin systems, callback registries) — not a
JIT-loader-specific convenience.

Unblocks the FunctionImport stub in wasmtime4j-provider's
WasmtimeModuleAdapter (deferred by F-Webassembly4j-LinkingContext-Imports-
Wiring-Fix charter B r.1 pending this method).
Bundles Charter A (Table interface completion), Charter B (LinkingContext
imports wiring fix), and Function.unwrap mini-arc. Local SNAPSHOT for
downstream Fiji jit-loader-java consumption before release cut to Maven
Central.
…cross-module store sharing

F-Webassembly4j-Cross-Module-Store-Sharing r.1. Adds default-throwing overload
Engine.loadModule(byte[] bytes, Instance shareStoreWith) so consumers can load
a related module against an existing instance's store — required for any
composition pattern where the new module imports memory/table/global exports
of the shared instance (JIT install, plugin loading, incremental linking,
multi-module workflows).

wasmtime4j-provider implements: unwraps shareStoreWith to native Instance,
extracts its Store via getStore(), reuses the store when constructing the
new WasmtimeModuleAdapter (which already accepted an explicit Store — no
refactor needed).

Non-wasmtime providers inherit UnsupportedOperationException default.

Disciplined per operator gate: cross-module store sharing is a general
Wasm-embedding pattern already used internally by wasmtime4j-provider's
own tests via ((WasmtimeModuleAdapter) module).store() escape. This surfaces
the capability at the api layer.

Compile clean. Tests to follow in a separate commit.
…dule(byte[], Instance)

Positive-witness test for F-Webassembly4j-Cross-Module-Store-Sharing r.1.
Uses the new engine-agnostic overload (no provider escape) to load a
consumer module against a producer instance's store, wires producer's
exported memory as a MemoryImport, and asserts consumer's store/load
helpers round-trip through the shared memory.

2 tests: happy-path round-trip + null-argument rejection.

Contrasts with WasmtimeLinkingContextExternImportsTest which uses
((WasmtimeModuleAdapter) module).store() provider escape for the same
scenario. Both patterns coexist post-charter.

All 88 wasmtime-provider tests pass. 162 api + 18 spi tests unchanged.
Charter: f-webassembly4j-caller-aware-host-function-charter-2026-07-26

Propagates the wasmtime4j r.2 / r.2.b Caller<T> pattern up to the
webassembly4j api layer so any provider can offer caller-aware host
functions engine-agnostically.
…nkingContext plumbing

Charter r.1-1. Engine-agnostic exposure of the wasmtime4j r.2 / r.2.b
Caller<T> scoped-mutation pattern.

- Caller<T>: 10 scoped methods (data, getMemory, getTable, getFunction,
  getGlobal, compileModule, instantiate, growTable, setTableElement,
  growMemory, unwrap).
- CallerAwareHostFunction<T>: @FunctionalInterface — Object[] execute(
  Caller<T>, Object...).
- CallerAwareHostFunctionDefinition: parallel to HostFunctionDefinition
  but wraps CallerAwareHostFunction.
- LinkingContext.callerAwareHostFunctions(): default returns empty list;
  providers that do not support the pattern inherit safe no-op behavior.
- DefaultLinkingContext.Builder.addCallerAwareHostFunction(...): two
  overloads matching addHostFunction shape.
…ler<T> as api Caller<T>

Bridges wasmtime4j's caller-scoped host-callback handle
(ai.tegmentum.wasmtime4j.func.Caller) into the webassembly4j api
Caller<T> interface added at r.1-1. Delegates each api method to the
underlying wasmtime4j Caller, wrapping/unwrapping types via existing
Wasmtime{Memory,Table,Function,Global,Instance}Adapter classes.

For instantiate(Module, LinkingContext), reconciles the api signature
against wasmtime4j's Caller.instantiate(InstancePre) by building a
transient linker from the caller's engine, calling instantiatePre on
it, then routing the pre through the caller's borrow-safe scoped
entrypoint. externImports are rejected at this path — they require a
live store binding that wasmtime4j's Caller does not expose.

compileModule returns a caller-scoped Module wrapper that has no
owning store; instantiation must go through Caller.instantiate.
…stFunctions from LinkingContext

Extends WasmtimeModuleAdapter.instantiate(LinkingContext) to consume
the new LinkingContext.callerAwareHostFunctions() list added at
r.1-1. Each CallerAwareHostFunctionDefinition is registered on the
linker as a wasmtime4j CallerAwareHostFunction — the subclass of
HostFunction whose execute runs with the native Caller available via
the CallerContextProvider SPI wired at wasmtime4j r.2. The native
caller is wrapped in a WasmtimeCallerAdapter and handed to the user's
CallerAwareHostFunction implementation.

Also adds a caller-scoped factory (WasmtimeModuleAdapter.callerScoped)
so WasmtimeCallerAdapter.compileModule can return a Module wrapper
that has no owning store; its own instantiate() paths throw with a
clear message pointing at Caller.instantiate. Extracts
defineHostFunctions to a package-private static helper for reuse
from WasmtimeCallerAdapter and adds a package-private nativeModule()
accessor for the caller-scoped instantiate bridge.
…e from callback

Hand-authored 88-byte wasm module imports env.trigger_grow, exports a
1-slot funcref table + memory, and calls trigger_grow(1) from run().
Test registers trigger_grow as a CallerAwareHostFunction whose
callback resolves the caller's table export via caller.getTable("table")
then grows it by 1 via caller.growTable — the borrow-safe scoped path
routed through the wasmtime4j r.2 caller handle. Asserts:

- pre-grow size observed inside the callback is 1
- growTable return value is the previous size (1)
- post-callback instance.table("table").size() is 2
- retained Caller handle used after callback return throws
  IllegalStateException with a caller-generation message
  (proves wasmtime4j's use-after-return generation counter propagates
  through the api-layer adapter unchanged)

Kept in the WasmtimeLinkingContextExternImportsTest style — inline
hand-authored wasm bytes so the test needs no build-time toolchain.
…d ops only

Initial test called t.size() from inside the caller callback via the
regular WasmtimeTableAdapter delegate; that path routes through
WasmTable.getSize which acquires the store lock, and inside a live
caller-borrow the JniTable native SIGSEGVs — witnessed via hs_err
crash at libwasmtime4j.dylib Table::size + JniTable_nativeGetSize.

Callback now:
- reads args via observedArg, not size()
- calls only caller.growTable (borrow-safe scoped path)

Also swaps the run(param i32) wasm to a run() no-param variant that
calls trigger_grow with an inline i32.const 1 — sidesteps the
pre-existing WasmtimeFunctionAdapter I_V fast-path bug where
(i32) -> () signatures route through callVoid() and drop the arg
("Parameter validation failed for function 'run'"). Wasm bytes
regenerated (88 -> 91 bytes).

Assertions unchanged: pre/post-callback table size, growTable return
value, use-after-return IllegalStateException from wasmtime4j r.2
generation counter.
…otes

Documents the full charter close: r.1-1 (api additions, landed
pre-partial), r.1-2 (WasmtimeCallerAdapter), r.1-3 (WasmtimeModuleAdapter
callerAwareHostFunctions consumption), r.1-4 (integration test + native
crash discovery), r.1-5 (mvn install SNAPSHOT refresh).

Notes the api adjustment reconciling Caller.instantiate(Module,
LinkingContext) at api layer against wasmtime4j's InstancePre-only
Caller.instantiate (transient linker + linker.instantiatePre inside
adapter). Notes the test-discovery finding that regular WasmTable/Memory
accessors SIGSEGV from callback frames — restated the wasmtime4j r.2
doctrine that mutation from callbacks MUST use caller-scoped ops.

r.5.c (F-JIT-Loader-Java-Reference Fiji retry) is UNBLOCKED.
…st wasmtime4j r.1 close)

Mirrors the wasmtime4j Caller-Scoped-Memory-IO r.1 additions at webassembly4j
api layer + wasmtime4j-provider bridge. Enables engine-agnostic scoped memory
I/O from caller-aware host callbacks — unblocks Fiji jit-loader r.5.d retry.

api: 2 default methods (throw UOE)
provider: WasmtimeCallerAdapter delegates to native Caller.readMemory/
writeMemory

Non-wasmtime providers inherit UOE default (safe).
F-Wasmtime4j-Caller-Scoped-Instantiate-Extern-Imports r.2. Replaces
WasmtimeCallerAdapter.instantiate's blanket LinkingException on
externImports with a per-def routing loop:

- MemoryImport / TableImport whose source is a WasmtimeMemoryAdapter /
  WasmtimeTableAdapter carrying a callerExportName (minted by
  Caller.getMemory/getTable in a callback frame) → route to the new
  caller-scoped linkerDefineMemoryFromExport / TableFromExport by-name
  native path (avoids registry-handle mismatch).

- MemoryImport / TableImport / GlobalImport with outer-scoped externs
  → route to linkerDefineMemory / Table / Global handle-based path.

- FunctionImport remains unsupported (waits on Function.unwrap).

WasmtimeMemoryAdapter / WasmtimeTableAdapter gain an optional
callerExportName field to signal caller-scoped origin; getMemory /
getTable on WasmtimeCallerAdapter set it.
F-Wasmtime4j-Caller-Scoped-API-Aligned-With-Wasmos-WIT r.1 CLOSED_SUCCEEDED
(with scope correction: doctrine applies at webassembly4j layer — the
portable engine abstraction — not at wasmtime4j which is wasmtime-specific
JNI binding). Per user 2026-07-27.

Class-level Javadoc gains a 'Design alignment' section citing the doctrine
+ translation rules (WIT kebab-case → Java camelCase, borrow<store>
removed since Caller has implicit store binding, result<T, error> →
throws, option<T> → Optional<T>, list<u8> → byte[]).

Per-method @see wasmos wit://... tags on 9 caller-scoped methods:
  getMemory/Table/Function/Global → instance.instance.get-*
  compileModule → module-compile.from-binary (deviation: engine implicit)
  instantiate → linker.linker.instantiate (deviation: LinkingContext
    bundles pre-linker define-* calls)
  growTable → instance.wasm-table.grow (upstream via r.2 of wasmos arc)
  setTableElement → instance.wasm-table.set (upstream via r.2)
  growMemory → instance.wasm-memory.grow
  readMemory → instance.wasm-memory.read (deviation: name-lookup vs borrow)
  writeMemory → instance.wasm-memory.write

12 @see-wasmos tags in file. Discoverable via grep. mvn compile green.
Bundled fixes shipped together during a wasmos-consumption push:

- CodeGenerator.generate() merges per-file BindgenModels before code
  emission. Previously each WIT file's javaCodeGenerator invocation
  emitted its own <RuntimeProvider>.java, and the last write silently
  overwrote earlier ones — killing SPI dispatchers for every interface
  but the last file processed. Test: WasmosRuntimeSpiMergeTest.

- BindgenCli.validateSources uses Files.walk instead of listFiles so
  `-w wit/deps` picks up every .wit under the tree. Combined with the
  merge fix, multi-file WIT packages resolve intra-package `use` refs
  correctly. Test: BindgenCliTest.shouldRecursivelyExpandDirectorySource.

- WitParser accepts stream<T> and future<T>: coerces to list<T> and
  option<T> respectively with a WARNING log rather than throwing
  BindgenException. Async component-model types are not modeled but the
  surrounding file stays parseable. Test: WitParserTest.asyncTypesCoerced.

- JavaCodeGenerator.mapType gains a TUPLE arm that recursively maps
  each element (was defaulting to embedding raw WIT text as a Java
  type name). TypeMappingRegistry.mapTuple emits parameterised
  Map.Entry<K,V> for 2-tuples (fits JDK; covers wasmos http/websocket
  headers shape) and parameterised TupleN placeholder otherwise. Test:
  NestedContainerFieldTest.

- ImplementationCodeGenerator passes parametrised Class<?>/Class<T>
  (not raw Class) to JavaPoet for WasmBindingProvider.supports/create
  overrides, resolving name-clash errors under erasure. Marshalling
  strategy branches on WIT element kind for list<T> params: real unbox
  loop for list<u8>/list<s8>, honest TODO-fallback for other elements.
  Tests: ImplementationCodeGeneratorBugsTest.

- MarshallingStrategy.liftReturn returns Optional<CodeBlock>; caller
  emits UnsupportedOperationException throw when Optional is empty
  (mirrors resultDispatch fallback). JavaCodeGenerator.shouldSkipInterface
  filters interface-and-record-with-same-name pairs (per ADR pattern
  in provider-manifest.wit) skipping emission with a warning rather
  than colliding on class name. Tests: InterfaceNestedTypeCollisionTest.

Suite: 458 -> 510 tests, all pass. Full 18-module install green.
Downstream effect of the bindgen SPI-merge + interface-skip fixes
landed in the preceding commit. Regenerated output for
wasmos:host/embedder@0.1.0 (~/git/wasm-cm) picks up:

- Correct SPI dispatchers when the WIT world spans multiple files.
- Split EmbedderApi / StringEncoding types that previously collided
  with the parent interface class name.
- Additional HostProviderMemory helper surface.

No manual edits — pure regeneration output.
Two new modules land together; together they let webassembly4j consumers
select the wasmos runtime as a provider alongside wasmtime4j / wamr4j /
endive / graalwasm.

wasmos-runtime-generated: bindgen output for wasmos:runtime@0.2.0 (the
portable frontend contract wasmos WASM control-planes target). The
generated Java types serve as the JNI-typed layer wasmos-provider
communicates with the Rust wasmos-runtime library through. 22 sources
plus a local copy of WitResult so downstream jars carry no bindgen
runtime dep.

wasmos-provider: implements EngineProvider (id "wasmos", priority 90)
via JNI to a Rust cdylib that wraps the wasmos-runtime library
(~/git/wasmos). Practical component-model surface end-to-end —
primitives + String + Optional + List + Map + Set (flags) + byte[]
fast path + records + variants + enums + tuples, plus typed carriers
for WitResource / WitFuture / WitStream / WitErrorContext. WASI-P2
full context passthrough via LinkingContext.wasiContext, ComponentConfig
honors all six limits (maxMemoryBytes, epochDeadline, fuelLimit,
maxTableElements, maxInstances, maxTables, maxMemories), component
serialize / deserialize for hot-reload. Sync invoke plus async slice
via WasmosAsyncExtension (invokeAsync returning CompletableFuture,
best-effort cancellation via epoch interruption, futures / streams /
error-context all park+close+pass-in wired — host-side reading of
future / stream values documented as bounded scope until wasmtime
ships dynamic-payload polling upstream).

Includes an E2E counter-resource test fixture built via cargo-component
+ wit-bindgen (checked-in source tree + rebuild README under
src/test/resources/counter-fixture-src/) plus 62 tests all passing
(19 Rust unit tests + 43 Java tests spanning marshalling, resource
lifecycle, async, WASI plumbing, ComponentConfig).

Rejections with helpful messages: LinkingContext.hostFunctions +
witHostFunctions + externImports (wasmos is WIT-first — use
wasmtime-provider for core-wasm host injection), Engine.loadModule
(wasmos is component-only), wasi:nn + wasi:http + per-endpoint egress
(needs wasmtime-wasi upstream).

Build setup requires a co-checked-out ~/git/wasmos tree AND sibling
~/git/wasm-cm + ~/git/wasm-continuity because wasmos-runtime declares
path deps to those siblings. Documented in wasmos-provider/README.md
and wasmos-provider/native/Cargo.toml. Blocks Maven Central publish
until wasmos + siblings publish versioned crates OR wasmos restructures
away from `path = "../<sibling>/..."`.
Swap the absolute path dep (`/Users/zacharywhitley/git/wasmos` —
only works on the original author's machine) for a relative path
(`../../../wasmos` from wasmos-provider/native/Cargo.toml). Anyone
with the standard sibling-checkout layout (~/git/webassembly4j +
~/git/wasmos + ~/git/wasm-cm + ~/git/wasm-continuity, or any other
common-parent arrangement) now gets a working build.

The path dep itself is unchanged in kind — still blocks external /
CI builds and Central publish until wasmos + wasm-cm + wasm-continuity
publish versioned crates or wasmos restructures away from
`path = "../<sibling>/..."` for its own deps. wasmos-provider/README.md
and Cargo.toml comment both spell out the tree-layout requirement.
… 16 updates

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

| Package | From | To |
| --- | --- | --- |
| [run.endive:runtime](https://github.com/bytecodealliance/endive) | `1.0.1` | `1.1.0` |
| [run.endive:wasm](https://github.com/bytecodealliance/endive) | `1.0.1` | `1.1.0` |
| [run.endive:wasi](https://github.com/bytecodealliance/endive) | `1.0.1` | `1.1.0` |
| [run.endive:compiler](https://github.com/bytecodealliance/endive) | `1.0.1` | `1.1.0` |
| [run.endive:wasm](https://github.com/bytecodealliance/endive) | `1.0.1` | `1.1.0` |
| [run.endive:wasi](https://github.com/bytecodealliance/endive) | `1.0.1` | `1.1.0` |
| [run.endive:compiler](https://github.com/bytecodealliance/endive) | `1.0.1` | `1.1.0` |
| [com.fasterxml.jackson.core:jackson-databind](https://github.com/FasterXML/jackson-databind) | `2.22.1` | `2.22.2` |
| [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.plugins:maven-failsafe-plugin](https://github.com/apache/maven-surefire) | `3.5.6` | `3.6.0` |
| [org.apache.maven.plugins:maven-jar-plugin](https://github.com/apache/maven-jar-plugin) | `3.5.0` | `3.5.1` |
| [org.codehaus.mojo:flatten-maven-plugin](https://github.com/mojohaus/flatten-maven-plugin) | `1.7.3` | `1.8.0` |
| [org.codehaus.mojo:exec-maven-plugin](https://github.com/mojohaus/exec-maven-plugin) | `3.6.3` | `3.6.4` |
| [org.apache.maven.plugin-tools:maven-plugin-annotations](https://github.com/apache/maven-plugin-tools) | `3.15.2` | `3.16.0` |
| [org.apache.maven.plugins:maven-plugin-plugin](https://github.com/apache/maven-plugin-tools) | `3.15.2` | `3.16.0` |
| [org.apache.maven.plugins:maven-failsafe-plugin](https://github.com/apache/maven-surefire) | `3.5.6` | `3.6.0` |
| [org.apache.maven.plugins:maven-antrun-plugin](https://github.com/apache/maven-antrun-plugin) | `3.1.0` | `3.2.0` |
| org.apache.maven:apache-maven | `3.9.9` | `3.9.16` |
| [org.apache.maven.wrapper:maven-wrapper](https://github.com/apache/maven-wrapper) | `3.2.0` | `3.3.4` |



Updates `run.endive:runtime` from 1.0.1 to 1.1.0
- [Release notes](https://github.com/bytecodealliance/endive/releases)
- [Commits](bytecodealliance/endive@1.0.1...1.1.0)

Updates `run.endive:wasm` from 1.0.1 to 1.1.0
- [Release notes](https://github.com/bytecodealliance/endive/releases)
- [Commits](bytecodealliance/endive@1.0.1...1.1.0)

Updates `run.endive:wasi` from 1.0.1 to 1.1.0
- [Release notes](https://github.com/bytecodealliance/endive/releases)
- [Commits](bytecodealliance/endive@1.0.1...1.1.0)

Updates `run.endive:compiler` from 1.0.1 to 1.1.0
- [Release notes](https://github.com/bytecodealliance/endive/releases)
- [Commits](bytecodealliance/endive@1.0.1...1.1.0)

Updates `run.endive:wasm` from 1.0.1 to 1.1.0
- [Release notes](https://github.com/bytecodealliance/endive/releases)
- [Commits](bytecodealliance/endive@1.0.1...1.1.0)

Updates `run.endive:wasi` from 1.0.1 to 1.1.0
- [Release notes](https://github.com/bytecodealliance/endive/releases)
- [Commits](bytecodealliance/endive@1.0.1...1.1.0)

Updates `run.endive:compiler` from 1.0.1 to 1.1.0
- [Release notes](https://github.com/bytecodealliance/endive/releases)
- [Commits](bytecodealliance/endive@1.0.1...1.1.0)

Updates `com.fasterxml.jackson.core:jackson-databind` from 2.22.1 to 2.22.2
- [Commits](FasterXML/jackson-databind@jackson-databind-2.22.1...jackson-databind-2.22.2)

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.plugins:maven-failsafe-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.plugins:maven-jar-plugin` from 3.5.0 to 3.5.1
- [Release notes](https://github.com/apache/maven-jar-plugin/releases)
- [Commits](apache/maven-jar-plugin@maven-jar-plugin-3.5.0...maven-jar-plugin-3.5.1)

Updates `org.codehaus.mojo:flatten-maven-plugin` from 1.7.3 to 1.8.0
- [Release notes](https://github.com/mojohaus/flatten-maven-plugin/releases)
- [Commits](mojohaus/flatten-maven-plugin@1.7.3...1.8.0)

Updates `org.codehaus.mojo:exec-maven-plugin` from 3.6.3 to 3.6.4
- [Release notes](https://github.com/mojohaus/exec-maven-plugin/releases)
- [Commits](mojohaus/exec-maven-plugin@3.6.3...3.6.4)

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

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

Updates `org.apache.maven.plugins:maven-failsafe-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.plugins:maven-antrun-plugin` from 3.1.0 to 3.2.0
- [Release notes](https://github.com/apache/maven-antrun-plugin/releases)
- [Commits](apache/maven-antrun-plugin@maven-antrun-plugin-3.1.0...maven-antrun-plugin-3.2.0)

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

Updates `org.apache.maven.wrapper:maven-wrapper` from 3.2.0 to 3.3.4
- [Release notes](https://github.com/apache/maven-wrapper/releases)
- [Commits](apache/maven-wrapper@maven-wrapper-3.2.0...maven-wrapper-3.3.4)

---
updated-dependencies:
- dependency-name: run.endive:runtime
  dependency-version: 1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: run.endive:wasm
  dependency-version: 1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: run.endive:wasi
  dependency-version: 1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: run.endive:compiler
  dependency-version: 1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: run.endive:wasm
  dependency-version: 1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: run.endive:wasi
  dependency-version: 1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: run.endive:compiler
  dependency-version: 1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: com.fasterxml.jackson.core:jackson-databind
  dependency-version: 2.22.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-compiler-plugin
  dependency-version: 3.16.0
  dependency-type: direct:production
  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:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-failsafe-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.plugins:maven-jar-plugin
  dependency-version: 3.5.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: org.codehaus.mojo:flatten-maven-plugin
  dependency-version: 1.8.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.codehaus.mojo:exec-maven-plugin
  dependency-version: 3.6.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugin-tools:maven-plugin-annotations
  dependency-version: 3.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-plugin-plugin
  dependency-version: 3.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
- dependency-name: org.apache.maven.plugins:maven-failsafe-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.plugins:maven-antrun-plugin
  dependency-version: 3.2.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
- dependency-name: org.apache.maven.wrapper:maven-wrapper
  dependency-version: 3.3.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-patch
...

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

dependabot Bot commented on behalf of github Sep 21, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies, java. 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 @github

dependabot Bot commented on behalf of github Sep 30, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Sep 30, 2026
@dependabot
dependabot Bot deleted the dependabot/maven/maven-minor-patch-553cac1d39 branch September 30, 2026 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants