[renovate]

This PR contains the following updates:

Package	Type	Update	Change
jdx/workflows	workflow	minor	v1.1.0 → v1.2.1

---

Release Notes

jdx/workflows

v1.2.1: : retry enforces timeout_minutes on macOS runners

Compare Source

The retry action now enforces timeout_minutes on runners that don't have timeout or gtimeout, such as hosted macOS runners.

Fixed

• retry: timeout_minutes now applies on runners without coreutils. In v1.2.0, the time limit only worked when timeout or gtimeout was on the PATH. Without either one, the action logged a warning and ran attempts with no limit. A hung attempt on a hosted macOS runner then ran until the job's own timeout and was never retried. When neither binary is available, the action now uses its own watchdog. It sends TERM to the attempt and all its child processes when the limit is reached, then sends KILL 30 seconds later, which matches timeout --kill-after=30. The attempt counts as failed and is retried. Runners that have timeout or gtimeout still use it, and timeout_minutes: 0 still means no limit. (#​18 by @​jdx)

  To get the fix, update your uses: jdx/workflows/retry@<sha> # v1.2.1 pin to the v1.2.1 commit.

Full Changelog: jdx/workflows@v1.2.0...v1.2.1

v1.2.0: : New retry and gpg-import composite actions

Compare Source

v1.2.0 adds two composite actions, retry and gpg-import. They run in bash and don't need Node, so they can replace nick-fields/retry and crazy-max/ghaction-import-gpg in jdx workflows.

Added

• retry action. Runs a command and runs it again if it fails or times out. It accepts the same nick-fields/retry inputs that mise uses: command, max_attempts (default 3), timeout_minutes (default 10; set it to 0 for no limit) and retry_wait_seconds (default 10). It doesn't support retry_on or timeout_seconds. Set shell: pwsh to run each attempt as PowerShell 7.3 or newer, for example on Windows runners. The time limit needs timeout or gtimeout on the PATH. On runners that have neither, such as macOS without coreutils, the action logs a warning and attempts have no time limit. After the last failed attempt, the step exits with the command's exit code. (#​16 by @​jdx)

  - uses: jdx/workflows/retry@<sha> # v1.2.0
    with:
      command: cargo test
      max_attempts: 2
      timeout_minutes: 30
      retry_wait_seconds: 30

• gpg-import action. Imports an ASCII-armored GPG private key and can set up git signing. The inputs are gpg_private_key, trust_level (1–5; leave it empty to keep the key untrusted), git_user_signingkey, git_commit_gpgsign and git_tag_gpgsign. The action outputs the key's fingerprint and keyid. Git settings are written to the global git config, so the step works before or after checkout. Keys protected by a passphrase are not supported. (#​16 by @​jdx)

  - uses: jdx/workflows/gpg-import@<sha> # v1.2.0
    with:
      gpg_private_key: ${{ secrets.GPG_KEY }}
      git_user_signingkey: true
      git_commit_gpgsign: true

Full Changelog: jdx/workflows@v1.1.2...v1.2.0

v1.1.2: : comment-release-fixes now actually runs the no-common-ancestor fix

Compare Source

v1.1.2 makes comment-release-fixes actually run the "no common ancestor" fix that v1.1.1 announced.

Fixed

• comment-release-fixes: the v1.1.1 ancestry fix now takes effect. The reusable workflow runs its shared script from a fixed commit of jdx/workflows. In v1.1.1, that pinned commit was still from before #​12, so the workflow kept failing with No common ancestor / cannot safely establish release ancestry whenever an earlier release tag shared no history with the new release. The pin now points to the merge of #​12. Release tags with no common ancestor are skipped, and the workflow uses the closest earlier release that is an ancestor. (#​14 by @​jdx)

  To upgrade, change your uses: jdx/workflows/.github/workflows/comment-release-fixes.yml@<sha> # v1.1.2 pin to the v1.1.2 commit. Pinning to v1.1.1 doesn't fix the error. If the job failed for a release, run the workflow again with workflow_dispatch to post its comments.

Full Changelog: jdx/workflows@v1.1.1...v1.1.2

v1.1.1: : comment-release-fixes no longer aborts on tags from unrelated history

Compare Source

comment-release-fixes now ignores earlier release tags that share no history with the new release, so it can still find the correct base release.

Fixed

• comment-release-fixes: release tags with no common ancestor are skipped. Some repositories have published releases from a separate history, for example after the repository was rewritten. GitHub's compare API returns No common ancestor (HTTP 404) for those tags. The workflow treated that error as fatal and failed with cannot safely establish release ancestry before it reached the real previous release. Because a tag with no common ancestor can't be an earlier release of the target, the workflow now skips it and uses the closest release that is an ancestor. Any other comparison error still stops the run without posting comments, so the range is never widened. (#​12 by @​jdx)

  To get the fix, update your uses: jdx/workflows/.github/workflows/comment-release-fixes.yml@<sha> # v1.1.1 pin to the v1.1.1 commit. To post comments for a release where the job failed, run the workflow again with workflow_dispatch.

Full Changelog: jdx/workflows@v1.1.0...v1.1.1

---

Configuration

📅 Schedule: (in timezone America/Chicago)

• Branch creation
  • Only on Friday (* * * * 5)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[greptile-apps]

This PR does not match any of the 1 configured review trigger rule.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Central YAML (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: 103042b8-a53a-4485-8c59-a3aa2c2c6064

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}