Update eniz1806/vaults3 Docker tag to v4.4.37 #320

2026-07-27T22:02:32+02:00

renovate-bot commented

2026-07-27 22:02:32 +02:00

This PR contains the following updates:

Package	Update	Change
eniz1806/vaults3	patch	`4.4.36` → `4.4.37`

Release Notes

Kodiqa-Solutions/VaultS3 (eniz1806/vaults3)

`v4.4.37`

Compare Source

Fixed

"Remember me" now pre-fills your credentials on the next login (issue #40). The
checkbox already persisted the session token (so you stayed signed in), but the
login form always started blank, so it did not "remember credentials" the way most
users expect. When checked, the dashboard now stores the access key (never the
secret) and pre-fills it, with the box pre-checked, on the next visit.

Added

vaults3-cli object verify <bucket> [--prefix=<p>] [--repair] to find and fix a
metadata/data desync (issue #40). If an object's metadata exists but its data is
missing, the object lists normally but a GET returns "Object not found" (it looks
present yet cannot be downloaded over S3). verify walks the bucket, probes each
object with a 1-byte ranged GET, and reports the keys whose data is unreadable;
--repair removes the orphaned metadata so the phantom stops appearing in listings.
It never touches readable objects. The S3 GET path also now logs a loud WARN
when it hits this desync, so it is diagnosable in server logs.

Notes

Folder "Last Modified" over rclone (issue #40, follow-up to #35) is an rclone
client limitation, not a server bug. VaultS3 already returns a <LastModified> on
<CommonPrefixes> (the #35 extension) and the web UI shows real folder dates, but
rclone does not read directory timestamps from S3 listings at all, so rclone lsd
shows folders with its own default date (e.g. 2000-01-01) regardless. There is
nothing to change server-side.

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.36` → `4.4.37` | --- ### Release Notes <details> <summary>Kodiqa-Solutions/VaultS3 (eniz1806/vaults3)</summary> ### [`v4.4.37`](https://github.com/Kodiqa-Solutions/VaultS3/blob/HEAD/CHANGELOG.md#4437---2026-07-27) [Compare Source](https://github.com/Kodiqa-Solutions/VaultS3/compare/v4.4.36...v4.4.37) ##### Fixed - **"Remember me" now pre-fills your credentials on the next login** (issue [#40](https://github.com/Kodiqa-Solutions/VaultS3/issues/40)). The checkbox already persisted the session token (so you stayed signed in), but the login form always started blank, so it did not "remember credentials" the way most users expect. When checked, the dashboard now stores the access key (never the secret) and pre-fills it, with the box pre-checked, on the next visit. ##### Added - **`vaults3-cli object verify <bucket> [--prefix=<p>] [--repair]`** to find and fix a metadata/data desync (issue [#40](https://github.com/Kodiqa-Solutions/VaultS3/issues/40)). If an object's metadata exists but its data is missing, the object lists normally but a `GET` returns "Object not found" (it looks present yet cannot be downloaded over S3). `verify` walks the bucket, probes each object with a 1-byte ranged `GET`, and reports the keys whose data is unreadable; `--repair` removes the orphaned metadata so the phantom stops appearing in listings. It never touches readable objects. The S3 `GET` path also now logs a loud `WARN` when it hits this desync, so it is diagnosable in server logs. ##### Notes - **Folder "Last Modified" over rclone (issue [#40](https://github.com/Kodiqa-Solutions/VaultS3/issues/40), follow-up to [#35](https://github.com/Kodiqa-Solutions/VaultS3/issues/35)) is an rclone client limitation, not a server bug.** VaultS3 already returns a `<LastModified>` on `<CommonPrefixes>` (the [#35](https://github.com/Kodiqa-Solutions/VaultS3/issues/35) extension) and the web UI shows real folder dates, but rclone does not read directory timestamps from S3 listings at all, so `rclone lsd` shows folders with its own default date (e.g. 2000-01-01) regardless. There is nothing to change server-side. </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. --- - [ ] 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-bot added 1 commit 2026-07-27 22:02:32 +02:00

Update eniz1806/vaults3 Docker tag to v4.4.37 39d9e75c65

renovate-bot scheduled this pull request to auto merge when all checks succeed 2026-07-27 22:02:33 +02:00

renovate-bot merged commit df281e0368 into main

2026-07-27 22:02:35 +02:00

renovate-bot deleted branch renovate/eniz1806-vaults3-4.x

2026-07-27 22:02:35 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: arnoutvw/compose-files#320