Update semaphoreui/semaphore Docker tag to v2.19.16 #319

Open

renovate-bot wants to merge 1 commit from renovate/semaphoreui-semaphore-2.x into main

pull from: renovate/semaphoreui-semaphore-2.x

merge into: enpls:main

enpls:main

enpls:renovate/traefik-3.x

enpls:renovate/codeberg.org-forgejo-forgejo-17.x

enpls:renovate/ghcr.io-jittering-traefik-kop-0.x

enpls:renovate/dxflrs-garage-2.x

enpls:renovate/redis-8.x

enpls:dev/magramai/more_backups

enpls:dev/outout/improve_services

enpls:conduwuit

enpls:dev/outout/fix_ci

Conversation 0 Commits 1 Files changed 1 +1 -1

renovate-bot commented 2026-08-25 21:15:56 +02:00

Collaborator

Copy link

This PR contains the following updates:

Package	Update	Change
semaphoreui/semaphore	patch	v2.19.8 → v2.19.16

---

Release Notes

semaphoreui/semaphore (semaphoreui/semaphore)

v2.19.16

Compare Source

Configurable runner check interval

Runners can now be told how often to ask the server for new jobs. Until now the interval was hard-coded to 1 second, which on installations with many runners produced a noticeable amount of request traffic.

New option in the runner section of the runner config:

{
  "runner": {
    "check_interval_seconds": 5
  }
}

Or via environment variable:

SEMAPHORE_RUNNER_CHECK_INTERVAL_SECONDS=5

Default: 1 second, so existing installations behave exactly as before. Values of 0, negative values, or values too large to represent as a duration fall back to the default.

What changes and what does not. Only the check for new jobs honours the configured interval. The runner's progress report, which also serves as its heartbeat, keeps running once per second. Raising the check interval therefore does not affect when the server marks a runner offline. Jobs will start up to check_interval_seconds later than before, so pick a value that matches how quickly you need new tasks to be picked up.

Affected components: runner (semaphore runner start), config schema. No database migration, no changes to the server or the web interface.

v2.19.15

Compare Source

v2.19.14

Compare Source

v2.19.12

Compare Source

Bogfixes

• Fixed bug with runner configuration on registration step.

v2.19.11

Compare Source

Changelog

• 0c3f373 test(db): add tests for db migration

v2.19.10

Compare Source

v2.19.9

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 has been generated by Mend Renovate.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [semaphoreui/semaphore](https://github.com/semaphoreui/semaphore) | patch | `v2.19.8` → `v2.19.16` | --- ### Release Notes <details> <summary>semaphoreui/semaphore (semaphoreui/semaphore)</summary> ### [`v2.19.16`](https://github.com/semaphoreui/semaphore/releases/tag/v2.19.16) [Compare Source](https://github.com/semaphoreui/semaphore/compare/v2.19.15...v2.19.16) #### Configurable runner check interval Runners can now be told how often to ask the server for new jobs. Until now the interval was hard-coded to 1 second, which on installations with many runners produced a noticeable amount of request traffic. New option in the runner section of the runner config: ``` { "runner": { "check_interval_seconds": 5 } } ``` Or via environment variable: ``` SEMAPHORE_RUNNER_CHECK_INTERVAL_SECONDS=5 ``` Default: 1 second, so existing installations behave exactly as before. Values of 0, negative values, or values too large to represent as a duration fall back to the default. What changes and what does not. Only the check for new jobs honours the configured interval. The runner's progress report, which also serves as its heartbeat, keeps running once per second. Raising the check interval therefore does not affect when the server marks a runner offline. Jobs will start up to check\_interval\_seconds later than before, so pick a value that matches how quickly you need new tasks to be picked up. Affected components: runner (semaphore runner start), config schema. No database migration, no changes to the server or the web interface. ### [`v2.19.15`](https://github.com/semaphoreui/semaphore/compare/v2.19.14...v2.19.15) [Compare Source](https://github.com/semaphoreui/semaphore/compare/v2.19.14...v2.19.15) ### [`v2.19.14`](https://github.com/semaphoreui/semaphore/compare/v2.19.12...v2.19.14) [Compare Source](https://github.com/semaphoreui/semaphore/compare/v2.19.12...v2.19.14) ### [`v2.19.12`](https://github.com/semaphoreui/semaphore/releases/tag/v2.19.12) [Compare Source](https://github.com/semaphoreui/semaphore/compare/v2.19.11...v2.19.12) #### Bogfixes - Fixed bug with runner configuration on registration step. ### [`v2.19.11`](https://github.com/semaphoreui/semaphore/releases/tag/v2.19.11) [Compare Source](https://github.com/semaphoreui/semaphore/compare/v2.19.10...v2.19.11) #### Changelog - [`0c3f373`](https://github.com/semaphoreui/semaphore/commit/0c3f3738ea5ed988165afe499d896ff78b428c44) test(db): add tests for db migration ### [`v2.19.10`](https://github.com/semaphoreui/semaphore/compare/v2.19.9...v2.19.10) [Compare Source](https://github.com/semaphoreui/semaphore/compare/v2.19.9...v2.19.10) ### [`v2.19.9`](https://github.com/semaphoreui/semaphore/compare/v2.19.8...v2.19.9) [Compare Source](https://github.com/semaphoreui/semaphore/compare/v2.19.8...v2.19.9) </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yODguMCIsInVwZGF0ZWRJblZlciI6IjQzLjI4OC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

renovate-bot added 1 commit 2026-08-25 21:15:57 +02:00

Update semaphoreui/semaphore Docker tag to v2.19.9 e69e9d3c82

renovate-bot force-pushed renovate/semaphoreui-semaphore-2.x from e69e9d3c82 to 4cee1dc1b9 2026-08-26 08:09:59 +02:00 Compare

renovate-bot changed title from Update semaphoreui/semaphore Docker tag to v2.19.9 to Update semaphoreui/semaphore Docker tag to v2.19.10 2026-08-26 08:10:15 +02:00

renovate-bot force-pushed renovate/semaphoreui-semaphore-2.x from 4cee1dc1b9 to e1c097f4f2 2026-08-26 16:00:04 +02:00 Compare

renovate-bot changed title from Update semaphoreui/semaphore Docker tag to v2.19.10 to Update semaphoreui/semaphore Docker tag to v2.19.11 2026-08-26 16:00:21 +02:00

renovate-bot force-pushed renovate/semaphoreui-semaphore-2.x from e1c097f4f2 to e3ab2337eb 2026-08-30 14:11:05 +02:00 Compare

renovate-bot changed title from Update semaphoreui/semaphore Docker tag to v2.19.11 to Update semaphoreui/semaphore Docker tag to v2.19.12 2026-08-30 14:11:28 +02:00

renovate-bot force-pushed renovate/semaphoreui-semaphore-2.x from e3ab2337eb to 5fbac92684 2026-09-09 15:24:01 +02:00 Compare

renovate-bot changed title from Update semaphoreui/semaphore Docker tag to v2.19.12 to Update semaphoreui/semaphore Docker tag to v2.19.14 2026-09-09 15:24:09 +02:00

renovate-bot force-pushed renovate/semaphoreui-semaphore-2.x from 5fbac92684 to e7cf6492be 2026-10-07 15:23:48 +02:00 Compare

renovate-bot changed title from Update semaphoreui/semaphore Docker tag to v2.19.14 to Update semaphoreui/semaphore Docker tag to v2.19.16 2026-10-07 15:23:55 +02:00

Some checks were skipped

Hide checks

lint / lint (pull_request) Has been skipped

Details

lint / lint (push) Has been skipped

Details

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin renovate/semaphoreui-semaphore-2.x:renovate/semaphoreui-semaphore-2.x

git switch renovate/semaphoreui-semaphore-2.x

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff renovate/semaphoreui-semaphore-2.x

git switch renovate/semaphoreui-semaphore-2.x

git rebase main

git switch main

git merge --ff-only renovate/semaphoreui-semaphore-2.x

git switch renovate/semaphoreui-semaphore-2.x

git rebase main

git switch main

git merge --no-ff renovate/semaphoreui-semaphore-2.x

git switch main

git merge --squash renovate/semaphoreui-semaphore-2.x

git switch main

git merge --ff-only renovate/semaphoreui-semaphore-2.x

git switch main

git merge renovate/semaphoreui-semaphore-2.x

git push origin main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

enpls/docker-services!319

No description provided.