From a7fb983236a423151455ce246902299ea7b9f882 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 22 Oct 2026 02:44:44 +0000 Subject: [PATCH 1/3] [tagpr] prepare for the next release --- gradle.properties | 2 +- nix/ajmx.nix | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/gradle.properties b/gradle.properties index de55ab6..a482420 100644 --- a/gradle.properties +++ b/gradle.properties @@ -1 +1 @@ -version=0.1.0 +version=0.1.1 diff --git a/nix/ajmx.nix b/nix/ajmx.nix index 972de2e..0089d7b 100644 --- a/nix/ajmx.nix +++ b/nix/ajmx.nix @@ -7,7 +7,7 @@ }: let - version = "0.1.0"; + version = "0.1.1"; graalvm = graalvmPackages.graalvm-ce; gradle = gradle_9.override { java = graalvm; }; fs = lib.fileset; From b13e85697a8c1d620f34beda971125a6665709aa Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 22 Oct 2026 02:44:48 +0000 Subject: [PATCH 2/3] build(deps-dev): bump wrangler from 4.143.0 to 4.146.0 in /docs (#43) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Bumps [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) from 4.143.0 to 4.146.0.
Release notes

Sourced from wrangler's releases.

wrangler@4.146.0

Minor Changes

Patch Changes

wrangler@4.145.0

Minor Changes

... (truncated)

Commits

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=wrangler&package-manager=npm_and_yarn&previous-version=4.143.0&new-version=4.146.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) ---
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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> From 360098d0fd01facddad4e218a57b9050d326616e Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 22 Oct 2026 02:44:52 +0000 Subject: [PATCH 3/3] build(nix): open a weekly PR that updates flake.lock (#22) ## Why `flake.lock` pins nixpkgs, flake-parts, treefmt-nix and git-hooks.nix, which decide GraalVM and Maven in the dev shell, the git hooks, and the toolchain of the `ajmx` Nix package. Dependabot does not cover flake inputs, and the lock has not changed since the initial commit, so the toolchain only moves when someone runs `nix flake update` by hand. verbatime opens a weekly pull request for this (yagipass/verbatime#111), and the CI of the two repositories should stay as close as possible. ## What - New `update-flake-lock` workflow, copied from verbatime. Every Monday at 00:00 UTC, and on manual dispatch, it runs `nix flake update --commit-lock-file` and opens or refreshes a pull request from `build/update-flake-lock` with the `dependencies` label. - A pull request opened with the workflow token does not start `pull_request` workflows, so the job starts `build.yml` on the branch with `gh workflow run`, and `build.yml` now accepts `workflow_dispatch`. The `tagpr` job only runs on `push`, so a dispatched run does not release. ## Trade-offs - If an update changes the `mvnHash`, the pull request is not fixed automatically and `checks` fails on it (#18). - `concurrency` with `cancel-in-progress`, which verbatime's `ci.yml` has, is not added to `build.yml`. Here the release jobs are in the same workflow, so a second push to `main` could cancel a release halfway. ## Verification Checked: - The pre-commit hooks pass, and the workflows parse as YAML. - The `create-pull-request` SHA is the `v8.1.1` tag, the latest release. - The repository allows Actions to create pull requests, as tagpr already relies on. - `install.sh` refers to `build.yml` only by its path, so it does not need to be regenerated. Not checked: - actionlint. - An actual run. Scheduled and manually dispatched runs need the workflow on `main`. - Whether the dispatched `build.yml` run satisfies the required checks of the `main` ruleset on the update pull request. ## After merging Run `gh workflow run update-flake-lock.yml` once, and check that it opens a pull request and that `build` runs on it. Closes #17