Home-Network/home-network-k3s-impl
2
0 Fork 0
Code Issues 2 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

chore(deps): Update semaphoreui/semaphore Docker tag to v2.19.17 #119

Merged
renovate-bot merged 1 commits from renovate/semaphoreui-semaphore-2.x into main 2026-11-07 08:26:05 +00:00
Conversation 0 Commits 1 Files Changed 2
+2 -2
renovate-bot commented 2026-11-07 08:16:57 +00:00
Collaborator
Copy link
Copy source

This PR contains the following updates:

Package Update Change
semaphoreui/semaphore patch v2.19.10 → v2.19.17

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

semaphoreui/semaphore

v2.19.17

Compare Source

Changelog
  • f8cefe6 feat(runner): add check interval configuration for job polling

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

Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • "after 3am and before 6am"
  • 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 these updates again.

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

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [semaphoreui/semaphore](https://github.com/semaphoreui/semaphore) | patch | `v2.19.10` → `v2.19.17` | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the [Dependency Dashboard](issues/91) for more information. --- ### Release Notes <details> <summary>semaphoreui/semaphore</summary> ### [`v2.19.17`](https://github.com/semaphoreui/semaphore/releases/tag/v2.19.17) [Compare Source](https://github.com/semaphoreui/semaphore/compare/v2.19.16...v2.19.17) ##### Changelog - [`f8cefe6`](https://github.com/semaphoreui/semaphore/commit/f8cefe62da4d40e536323e3dd936eb2e04e82b1a) feat(runner): add check interval configuration for job polling ### [`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 </details> --- ### Configuration 📅 **Schedule**: (in timezone America/New_York) - Branch creation - "after 3am and before 6am" - 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 these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNjcuMCIsInVwZGF0ZWRJblZlciI6IjQ0LjE2Ny4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJhdXRvbWF0ZWQtdXBkYXRlIiwiZGVwZW5kZW5jaWVzIl19-->
renovate-bot added the dependenciesautomated-update labels 2026-11-07 08:16:57 +00:00
renovate-bot added 1 commit 2026-11-07 08:16:58 +00:00
chore(deps): Update semaphoreui/semaphore Docker tag to v2.19.17
gate / gate (pull_request) Successful in 2m58s
Details
gate / conformance (pull_request) Has been skipped
Details
b7cb70955c
renovate-bot scheduled this pull request to auto merge when all checks succeed 2026-11-07 08:16:58 +00:00
renovate-bot merged commit 5e8b080298 into main 2026-11-07 08:26:05 +00:00
renovate-bot deleted branch renovate/semaphoreui-semaphore-2.x 2026-11-07 08:26:05 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
agent
automated-update
blast-radius
breaking
ci-tooling
dependencies
needs-review
own-image
range-widen
No labels automated-update dependencies
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
gitea-admin jakman85 (Keith Jackson) pm-agent renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Home-Network/home-network-k3s-impl#119