build(deps): bump io.papermc.paper:paper-api from 1.21.1-R0.1-SNAPSHOT to 26.1.2.build.74-stable in /folia-phantom#89
Conversation
Bumps io.papermc.paper:paper-api from 1.21.1-R0.1-SNAPSHOT to 26.1.2.build.74-stable. --- updated-dependencies: - dependency-name: io.papermc.paper:paper-api dependency-version: 26.1.2.build.74-stable dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2d2370c0c6
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| <maven.compiler.target>17</maven.compiler.target> | ||
| <asm.version>9.7</asm.version> | ||
| <paper.version>1.21.1-R0.1-SNAPSHOT</paper.version> | ||
| <paper.version>26.1.2.build.74-stable</paper.version> |
There was a problem hiding this comment.
This managed paper-api version is used by both the core and plugin modules, but Paper's setup for 26.1.2 uses a Java 25 toolchain. The repo still verifies only on Java 17/21 in .github/workflows/ci.yml (java: ['17', '21'] and mvn ... verify), so after Maven resolves this API the configured CI builds no longer have a new enough JDK. Please either keep a Java-21-compatible Paper API or update the build/CI toolchain with this bump.
Useful? React with 👍 / 👎.
Bumps io.papermc.paper:paper-api from 1.21.1-R0.1-SNAPSHOT to 26.1.2.build.74-stable.
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)