Update eniz1806/vaults3 Docker tag to v4.4.14 #293

Merged
renovate-bot merged 1 commits from renovate/eniz1806-vaults3-4.x into main 2026-07-10 22:02:00 +02:00
Collaborator

This PR contains the following updates:

Package Update Change
eniz1806/vaults3 patch 4.4.12 → 4.4.14

⚠️ Warning

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


Release Notes

Kodiqa-Solutions/VaultS3 (eniz1806/vaults3)

v4.4.14

Compare Source

Fixed
  • Cluster capacity now gathers peer info over the cluster channel (issue #​29).
    The coordinator built the rollup by logging in to each peer's dashboard /api/v1
    API, which is unreachable peer-to-peer in split-console_port or proxied
    (Kubernetes + Envoy) deployments — every remote node showed as unreachable while
    only the node serving the request appeared. Nodes now expose their capacity on a
    new cluster-secret-authenticated /cluster/sysinfo endpoint (served next to
    /cluster/status), and the coordinator fetches it over the same peer addresses
    the placement proxy already uses for S3 forwarding — no dashboard login, no
    console-port dependency. Response is assembled server-side.

v4.4.13

Compare Source

Installation

Docker (recommended):

docker pull eniz1806/vaults3:v4.4.13

Binary download:
Download the archive for your platform below, extract, and run:

tar xzf vaults3-<os>-<arch>.tar.gz
./vaults3

Supported platforms: Linux (amd64, arm64), macOS (amd64, arm64), Windows (amd64)


Full Changelog: https://github.com/Kodiqa-Solutions/VaultS3/compare/v4.4.12...v4.4.13


Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 | |---|---|---| | [eniz1806/vaults3](https://github.com/Kodiqa-Solutions/VaultS3) | patch | `4.4.12` → `4.4.14` | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the [Dependency Dashboard](issues/3) for more information. --- ### Release Notes <details> <summary>Kodiqa-Solutions/VaultS3 (eniz1806/vaults3)</summary> ### [`v4.4.14`](https://github.com/Kodiqa-Solutions/VaultS3/blob/HEAD/CHANGELOG.md#4414---2026-07-10) [Compare Source](https://github.com/Kodiqa-Solutions/VaultS3/compare/v4.4.13...v4.4.14) ##### Fixed - **Cluster capacity now gathers peer info over the cluster channel** (issue [#&#8203;29](https://github.com/Kodiqa-Solutions/VaultS3/issues/29)). The coordinator built the rollup by logging in to each peer's dashboard `/api/v1` API, which is unreachable peer-to-peer in split-`console_port` or proxied (Kubernetes + Envoy) deployments — every remote node showed as unreachable while only the node serving the request appeared. Nodes now expose their capacity on a new cluster-secret-authenticated `/cluster/sysinfo` endpoint (served next to `/cluster/status`), and the coordinator fetches it over the same peer addresses the placement proxy already uses for S3 forwarding — no dashboard login, no console-port dependency. Response is assembled server-side. ### [`v4.4.13`](https://github.com/Kodiqa-Solutions/VaultS3/releases/tag/v4.4.13) [Compare Source](https://github.com/Kodiqa-Solutions/VaultS3/compare/v4.4.12...v4.4.13) #### Installation **Docker (recommended):** ```bash docker pull eniz1806/vaults3:v4.4.13 ``` **Binary download:** Download the archive for your platform below, extract, and run: ```bash tar xzf vaults3-<os>-<arch>.tar.gz ./vaults3 ``` **Supported platforms:** Linux (amd64, arm64), macOS (amd64, arm64), Windows (amd64) *** **Full Changelog**: <https://github.com/Kodiqa-Solutions/VaultS3/compare/v4.4.12...v4.4.13> </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, 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:eyJjcmVhdGVkSW5WZXIiOiI0My4yNTcuNCIsInVwZGF0ZWRJblZlciI6IjQzLjI1Ny40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->
renovate-bot added 1 commit 2026-07-10 22:01:59 +02:00
renovate-bot scheduled this pull request to auto merge when all checks succeed 2026-07-10 22:01:59 +02:00
renovate-bot merged commit 1309b29951 into main 2026-07-10 22:02:00 +02:00
renovate-bot deleted branch renovate/eniz1806-vaults3-4.x 2026-07-10 22:02:01 +02:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: arnoutvw/compose-files#293