Bump the "dependencies" group with 2 updates across multiple ecosystems

[dependabot]

Bumps the dependencies group with 2 updates: actions/upload-pages-artifact and actions/github-script.

Updates actions/upload-pages-artifact from 4 to 5

Release notes

Sourced from actions/upload-pages-artifact's releases.

v5.0.0

Changelog

• Update upload-artifact action to version 7 @​Tom-van-Woudenberg (#139)
• feat: add include-hidden-files input @​jonchurch (#137)

See details of all code changes since previous release.

Commits

• fc324d3 Merge pull request #139 from Tom-van-Woudenberg/patch-1
• fe9d4b7 Merge branch 'main' into patch-1
• 0ca1617 Merge pull request #137 from jonchurch/include-hidden-files
• 57f0e84 Update action.yml
• 4a90348 v7 --> hash
• 56f665a Update upload-artifact action to version 7
• f7615f5 Add include-hidden-files input
• See full diff in compare view

Updates actions/github-script from 8 to 9

Release notes

Sourced from actions/github-script's releases.

v9.0.0

New features:

• getOctokit factory function — Available directly in the script context. Create additional authenticated Octokit clients with different tokens for multi-token workflows, GitHub App tokens, and cross-org access. See Creating additional clients with getOctokit for details and examples.
• Orchestration ID in user-agent — The ACTIONS_ORCHESTRATION_ID environment variable is automatically appended to the user-agent string for request tracing.

Breaking changes:

• require('@actions/github') no longer works in scripts. The upgrade to @actions/github v9 (ESM-only) means require('@actions/github') will fail at runtime. If you previously used patterns like const { getOctokit } = require('@actions/github') to create secondary clients, use the new injected getOctokit function instead — it's available directly in the script context with no imports needed.
• getOctokit is now an injected function parameter. Scripts that declare const getOctokit = ... or let getOctokit = ... will get a SyntaxError because JavaScript does not allow const/let redeclaration of function parameters. Use the injected getOctokit directly, or use var getOctokit = ... if you need to redeclare it.
• If your script accesses other @actions/github internals beyond the standard github/octokit client, you may need to update those references for v9 compatibility.

What's Changed

• Add ACTIONS_ORCHESTRATION_ID to user-agent string by @​Copilot in actions/github-script#695
• ci: use deployment: false for integration test environments by @​salmanmkc in actions/github-script#712
• feat!: add getOctokit to script context, upgrade @​actions/github v9, @​octokit/core v7, and related packages by @​salmanmkc in actions/github-script#700

New Contributors

• @​Copilot made their first contribution in actions/github-script#695

Full Changelog: actions/github-script@v8.0.0...v9.0.0

Commits

• 3a2844b Merge pull request #700 from actions/salmanmkc/expose-getoctokit + prepare re...
• ca10bbd fix: use @​octokit/core/types import for v7 compatibility
• 86e48e2 merge: incorporate main branch changes
• c108472 chore: rebuild dist for v9 upgrade and getOctokit factory
• afff112 Merge pull request #712 from actions/salmanmkc/deployment-false + fix user-ag...
• ff8117e ci: fix user-agent test to handle orchestration ID
• 81c6b78 ci: use deployment: false to suppress deployment noise from integration tests
• 3953caf docs: update README examples from @​v8 to @​v9, add getOctokit docs and v9 brea...
• c17d55b ci: add getOctokit integration test job
• a047196 test: add getOctokit integration tests via callAsyncFunction
• Additional commits viewable in compare view

Bumps the dependencies group with 3 updates: nl.jqno.equalsverifier:equalsverifier, org.itsallcode:simple-process and io.github.git-commit-id:git-commit-id-maven-plugin.

Updates nl.jqno.equalsverifier:equalsverifier from 4.4.1 to 4.5

Release notes

Sourced from nl.jqno.equalsverifier:equalsverifier's releases.

Release equalsverifier-4.5

For a list of changes in this version, see CHANGELOG.md.

Release equalsverifier-4.4.2

For a list of changes in this version, see CHANGELOG.md.

Changelog

Sourced from nl.jqno.equalsverifier:equalsverifier's changelog.

[4.5] - 2026-04-17

Added

• EqualsVerifier now detects when java.net.URL fields are used in equals or hashCode, since URL.equals() and URL.hashCode() perform DNS resolution, making them network-dependent and non-deterministic. Consider using URI.create(url.toString()) instead. This check can be suppressed with Warning.URL_EQUALITY. (Issue #1203)

[4.4.2] - 2026-04-07

Changed

• Multi-line error messages now align better.

Fixed

• Fixes a bug where a NoSuchElementException was thrown when verifying a Kotlin class that inherits a private val lazy property from a parent class (Issue 1170).
• Fixes a bug where static fields of certain types (e.g., BigDecimal and boxed Float) were not restored to their original value after EqualsVerifier threw a NullPointerException while null-checking them.
• Fixes a bug where an Enum<?> field resolved to Enum<Enum<Object>> (because Enum has a self-referential type bound).

Commits

• 3f72cbc Bumps version to 4.5
• abd5aa9 Updates CHANGELOG for release
• 04f89c1 Merge pull request #1204 from jqno/add-url-fieldcheck
• ffc7f03 Streamlines UrlTest
• e9cf3be Adds URL FieldCheck
• 472e8b1 Update copyright year in README.md
• 94ebdf6 Merge pull request #1202 from jqno/vendors-signedjar-test
• 8d6327d Excludes equalsverifier-test-signedjar from PITest coverage
• 7b828dc All signed-jar tests should run via failsafe so it runs through the actual ja...
• 377c217 Incorporates SignedJarTest from separate repository
• Additional commits viewable in compare view

Updates org.itsallcode:simple-process from 0.3.1 to 0.3.2

Release notes

Sourced from org.itsallcode:simple-process's releases.

Release 0.3.2

[0.3.2] - 2026-04-18

• [PR #17](itsallcode/simple-process#17): Upgrade dependencies

Changelog

Sourced from org.itsallcode:simple-process's changelog.

[0.3.2] - 2026-04-18

• [PR #17](itsallcode/simple-process#17): Upgrade dependencies

Commits

• 7b6bef2 Bump the "dependencies" group with 2 updates across multiple ecosystems (#17)
• 46eddba Bump the dependencies group across 1 directory with 2 updates (#16)
• 61f20c6 Bump the dependencies group with 2 updates (#15)
• 25232f9 Bump actions/checkout from 5 to 6 in the dependencies group (#14)
• 37622c2 Bump github/codeql-action from 3 to 4 in the dependencies group (#13)
• See full diff in compare view

Updates io.github.git-commit-id:git-commit-id-maven-plugin from 9.1.0 to 10.0.0

Release notes

Sourced from io.github.git-commit-id:git-commit-id-maven-plugin's releases.

Version 10.0.0 is finally there and includes various bug-fixes and improvements :-)

⚠️ This is a potentially breaking release. Read the release-notes carefully ⚠️

Potential Breaking changes:

The main key-aspects that might cause a breakage when migrating to the new version:

• #913 / #914: Require Maven 3.9.0 [Maven 3.6.3 is EOL] ⚠️

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>10.0.0</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.

Known Issues / Limitations:

• This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in ktoso/maven-git-commit-id-plugin#279
• Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to git-commit-id/maven-git-commit-id-plugin#287 or git-commit-id/maven-git-commit-id-plugin#413 for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Full Changelog: git-commit-id/git-commit-id-maven-plugin@v9.2.0...v10.0.0

Version 9.2.0 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the following:

• bump several plugins
  • bump io.github.git-commit-id:git-commit-id-plugin-core from 6.1.5 to 6.2.0
    • replace org.eclipse.jgit.ssh.jsch with org.eclipse.jgit:org.eclipse.jgit.ssh.apache (see https://github.com/eclipse-jgit/jgit/blob/master/org.eclipse.jgit.ssh.jsch/README.md)

... (truncated)

Commits

• 2cd9c8b Bump version: 9.2.0 → 10.0.0
• fbfc066 Merge pull request #914 from git-commit-id/maven_3_9_0
• 3d51706 git-commit-id/git-commit-id-maven-plugin#913: Requi...
• fd9a262 update to the latest version available
• 0163ad6 Bump version: 9.1.0 → 9.2.0
• d8fdbb3 Merge pull request #912 from git-commit-id/plugin-core_6_2_0
• 8a33505 bump io.github.git-commit-id:git-commit-id-plugin-core from 6.1.5 to 6.2.0
• 4aefc60 update to the latest version in readme
• 743c415 update links to git-commit-id-maven-plugin (we are not in the core module :-)
• See full diff in compare view

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