martin/cluster

Watch

Fork 0

chore(deps): update dependency arnarg/nixidy to v0.22.1 #43

Merged

martin merged 2 commits from renovate/arnarg-nixidy-0.x into main

2026-07-28 16:44:07 +00:00

clank-bot commented

2026-07-28 00:00:32 +00:00

Collaborator

This PR contains the following updates:

Package	Update	Change
arnarg/nixidy	patch	`v0.22.0` → `v0.22.1`

Release Notes

arnarg/nixidy (arnarg/nixidy)

`v0.22.1`

Compare Source

Pin your project settings with `.nixidy.json`

If you're working in a flake-less or devenv project, you've probably found yourself repeating the same --devenv or -f flags on every nixidy invocation, or relying on the auto-detection heuristics to figure out how your environment should be built. Now you can commit those choices once.

Drop a .nixidy.json in your project root:

{
  "devenv": true,
  "file": "k8s.nix"
}

The CLI picks it up automatically. devenv pins whether the devenv build backend is used, and file sets the entrypoint nix file for flake-less builds. Both are optional, so you can set just the one you care about.

The --devenv flag has grown into --devenv/--no-devenv so you can override the config in either direction from the command line. Resolution order is:

CLI flag (--devenv / --no-devenv)
.nixidy.json
Auto-detection (e.g. devenv.nix present, no flake.nix)

The entrypoint file follows the same pattern: --file wins, then the config, then the default.nix default.

Bug Fixes

CRDs now apply with server-side apply. Large CRDs can exceed the annotation size limit that client-side apply imposes, and server-side apply is itself incompatible with nixidy's label-based pruning. nixidy apply now applies CRDs with --server-side --force-conflicts and skips pruning for the CRDs class only. Namespaces and regular manifests keep their existing prune behavior. #83 65cea87

Improvements

Switched to nixfmt. nixidy now formats with the nixfmt package instead of nixfmt-rfc-style, which has been merged upstream into nixfmt. #106 @0z13

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 | |---|---|---| | [arnarg/nixidy](https://github.com/arnarg/nixidy) | patch | `v0.22.0` → `v0.22.1` | --- ### Release Notes <details> <summary>arnarg/nixidy (arnarg/nixidy)</summary> ### [`v0.22.1`](https://github.com/arnarg/nixidy/releases/tag/v0.22.1) [Compare Source](https://github.com/arnarg/nixidy/compare/v0.22.0...v0.22.1) #### Pin your project settings with `.nixidy.json` If you're working in a flake-less or devenv project, you've probably found yourself repeating the same `--devenv` or `-f` flags on every `nixidy` invocation, or relying on the auto-detection heuristics to figure out how your environment should be built. Now you can commit those choices once. Drop a `.nixidy.json` in your project root: ```json { "devenv": true, "file": "k8s.nix" } ``` The CLI picks it up automatically. `devenv` pins whether the devenv build backend is used, and `file` sets the entrypoint nix file for flake-less builds. Both are optional, so you can set just the one you care about. The `--devenv` flag has grown into `--devenv/--no-devenv` so you can override the config in either direction from the command line. Resolution order is: 1. **CLI flag** (`--devenv` / `--no-devenv`) 2. **`.nixidy.json`** 3. **Auto-detection** (e.g. `devenv.nix` present, no `flake.nix`) The entrypoint file follows the same pattern: `--file` wins, then the config, then the `default.nix` default. #### Bug Fixes - **CRDs now apply with server-side apply.** Large CRDs can exceed the annotation size limit that client-side apply imposes, and server-side apply is itself incompatible with nixidy's label-based pruning. `nixidy apply` now applies CRDs with `--server-side --force-conflicts` and skips pruning for the CRDs class only. Namespaces and regular manifests keep their existing prune behavior. [#83](https://github.com/arnarg/nixidy/issues/83) [`65cea87`](https://github.com/arnarg/nixidy/commit/65cea8784aaf6d0f9cdeeeda2b7eabde375e2a2b) #### Improvements - **Switched to `nixfmt`.** nixidy now formats with the `nixfmt` package instead of `nixfmt-rfc-style`, which has been merged upstream into `nixfmt`. [#106](https://github.com/arnarg/nixidy/issues/106) [@0z13](https://github.com/0z13) </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. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).

clank-bot added 1 commit

2026-07-28 00:00:32 +00:00

chore(deps): update dependency arnarg/nixidy to v0.22.1

ci/woodpecker/pr/pr-review Pipeline was successful

Details

ci/woodpecker/pr/switch Pipeline was successful

Details

9438f36ed3

clank-bot requested review from martin

2026-07-28 00:00:33 +00:00

clank-bot added 1 commit

2026-07-28 00:06:23 +00:00

chore: update flake.lock [CI SKIP]

ci/woodpecker/pr/pr-review Pipeline was successful

Details

ci/woodpecker/pr/switch Pipeline was successful

Details

09b2bd636e

clank-bot commented

2026-07-28 14:54:50 +00:00

Author

Collaborator

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

### Edited/Blocked Notification Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠️ **Warning**: custom changes will be lost.