chore(deps): update dependency fnox to v1.33.0 #8

Merged

rosa merged 1 commit from renovate/fnox-1.x into main

2026-08-20 14:14:56 +00:00

rosa commented

2026-08-17 16:03:13 +00:00

Owner

This PR contains the following updates:

Package	Type	Update	Change	Pending
fnox	tools	minor	`1.32.0` → `1.33.0`	`v1.33.1`

Release Notes

jdx/fnox (fnox)

`v1.33.0`: : Bitwarden custom fields

Compare Source

A small release that adds custom field support to the Bitwarden provider, plus a documentation cleanup for personal age-based sync. The rest of the release is routine dependency and CI maintenance.

Added

Bitwarden custom field support (#690) -- @jdx. In addition to the standard username, password, notes, uri, and totp fields, any other field name in a item/field reference is now resolved as a custom field. With the default bw backend, fnox fetches the full item JSON and extracts the matching field (case-sensitive); with the rbw backend it uses the --field flag.
```
API_KEY = { provider = "bitwarden", value = "Database/API Key" }
```

Fixed

Bitwarden custom field names containing slashes (#693) -- @jdx. References now split only on the first /, so custom field names such as Database/API/Key resolve correctly. This also removes the previous "too many slashes" error for references with more than one /.

Documentation

Clarified personal age provider setup for sync (#692) -- @jdx. The sync guide now uses a dedicated sync-age provider with the --local-file flag, corrects the invalid fnox set --provider age setup step, explains how provider definitions replace by name rather than deep-merging, and distinguishes a personal sync cache from team-encrypted secrets in git.

Full Changelog: https://github.com/jdx/fnox/compare/v1.32.0...v1.33.0

fnox is maintained by @jdx, an open source developer for entire.io, the title sponsor of the jdx.dev open source tools including mise, aube, hk, and more. Keeping fnox secure, maintained, and free is funded by sponsors.

If fnox is handling secrets or config for you or your team, please consider sponsoring at jdx.dev. Sponsorships are what let fnox stay independent and the project keep moving.

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 | Type | Update | Change | Pending | |---|---|---|---|---| | [fnox](https://github.com/jdx/fnox) | tools | minor | `1.32.0` → `1.33.0` | `v1.33.1` | --- ### Release Notes <details> <summary>jdx/fnox (fnox)</summary> ### [`v1.33.0`](https://github.com/jdx/fnox/releases/tag/v1.33.0): : Bitwarden custom fields [Compare Source](https://github.com/jdx/fnox/compare/v1.32.0...v1.33.0) A small release that adds custom field support to the Bitwarden provider, plus a documentation cleanup for personal age-based sync. The rest of the release is routine dependency and CI maintenance. #### Added - **Bitwarden custom field support** ([#690](https://github.com/jdx/fnox/pull/690)) -- [@jdx](https://github.com/jdx). In addition to the standard `username`, `password`, `notes`, `uri`, and `totp` fields, any other field name in a `item/field` reference is now resolved as a custom field. With the default `bw` backend, fnox fetches the full item JSON and extracts the matching field (case-sensitive); with the `rbw` backend it uses the `--field` flag. ```toml API_KEY = { provider = "bitwarden", value = "Database/API Key" } ``` #### Fixed - **Bitwarden custom field names containing slashes** ([#693](https://github.com/jdx/fnox/pull/693)) -- [@jdx](https://github.com/jdx). References now split only on the first `/`, so custom field names such as `Database/API/Key` resolve correctly. This also removes the previous "too many slashes" error for references with more than one `/`. #### Documentation - **Clarified personal age provider setup for sync** ([#692](https://github.com/jdx/fnox/pull/692)) -- [@jdx](https://github.com/jdx). The sync guide now uses a dedicated `sync-age` provider with the `--local-file` flag, corrects the invalid `fnox set --provider age` setup step, explains how provider definitions replace by name rather than deep-merging, and distinguishes a personal sync cache from team-encrypted secrets in git. **Full Changelog**: <https://github.com/jdx/fnox/compare/v1.32.0...v1.33.0> #### 💚 Sponsor fnox fnox is maintained by [@jdx](https://github.com/jdx), an open source developer for [**entire.io**](https://entire.io), the title sponsor of the [jdx.dev](https://jdx.dev) open source tools including [mise](https://mise.jdx.dev/), [aube](https://aube.jdx.dev/), hk, and more. Keeping fnox secure, maintained, and free is funded by sponsors. If fnox is handling secrets or config for you or your team, please consider [sponsoring at jdx.dev](https://jdx.dev/sponsors.html). Sponsorships are what let fnox stay independent and the project keep moving. </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).

rosa added 1 commit

2026-08-17 16:03:13 +00:00