Update flake/home-manager/flake.lock

[github-actions]

Automated changes by the update-flake-lock GitHub Action.

Flake lock file updates:

• Updated input 'caelestia-cli':
    'github:caelestia-dots/cli/78e0b9d795dc38fb63cfc5a59cb7fa6038a757ed' (2025-12-23)
  → 'github:caelestia-dots/cli/f3ea42d43a07a13ba932d3b66515efbe51b3f532' (2025-12-29)
• Updated input 'caelestia-cli/caelestia-shell':
    'github:caelestia-dots/shell/66e509ae488b2c0468f2c803fd34c2625ca725dc' (2025-12-21)
  → 'github:caelestia-dots/shell/dfa28d7f85215bd42d02717255c45b8126aeb8da' (2025-12-28)
• Updated input 'caelestia-cli/caelestia-shell/quickshell':
    'git+https://git.outfoxxed.me/outfoxxed/quickshell?ref=refs/heads/master&rev=26531fc46ef17e9365b03770edd3fb9206fcb460' (2025-12-02)
  → 'git+https://git.outfoxxed.me/outfoxxed/quickshell?ref=refs/heads/master&rev=41828c4180fb921df7992a5405f5ff05d2ac2fff' (2025-12-26)
• Updated input 'caelestia-shell':
    'github:caelestia-dots/shell/66e509ae488b2c0468f2c803fd34c2625ca725dc' (2025-12-21)
  → 'github:caelestia-dots/shell/dfa28d7f85215bd42d02717255c45b8126aeb8da' (2025-12-28)
• Updated input 'caelestia-shell/quickshell':
    'git+https://git.outfoxxed.me/outfoxxed/quickshell?ref=refs/heads/master&rev=26531fc46ef17e9365b03770edd3fb9206fcb460' (2025-12-02)
  → 'git+https://git.outfoxxed.me/outfoxxed/quickshell?ref=refs/heads/master&rev=41828c4180fb921df7992a5405f5ff05d2ac2fff' (2025-12-26)
• Updated input 'firefox-ultima':
    'github:soulhotel/FF-ULTIMA/22640ef05506f1ac9c4cb00fcea26fc09144a08c' (2025-12-19)
  → 'github:soulhotel/FF-ULTIMA/f1d855ae20940909c7247c1828c0e4b2c7bba9ac' (2025-12-30)
• Updated input 'home-manager':
    'github:nix-community/home-manager/7eca7f7081036a7b740090994c9ec543927f89a7' (2025-12-24)
  → 'github:nix-community/home-manager/e4e78a2cbeaddd07ab7238971b16468cc1d14daf' (2025-12-30)
• Updated input 'nix4vscode':
    'github:nix-community/nix4vscode/c04ac687a5f53e05f5c66298ec23fb39f2a22cb9' (2025-12-24)
  → 'github:nix-community/nix4vscode/f44c3d6e2b95fd4e482883baf65c1fa7ea416078' (2026-01-01)
• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/a6531044f6d0bef691ea18d4d4ce44d0daa6e816' (2025-12-21)
  → 'github:NixOS/nixpkgs/cad22e7d996aea55ecab064e84834289143e44a0' (2025-12-30)
• Updated input 'sops-nix':
    'github:Mic92/sops-nix/9836912e37aef546029e48c8749834735a6b9dad' (2025-12-21)
  → 'github:Mic92/sops-nix/61b39c7b657081c2adc91b75dd3ad8a91d6f07a7' (2025-12-28)
• Updated input 'vicinae':
    'github:vicinaehq/vicinae/7204a77bd8dc5f8857ec2f1521b2027c26e6bb04' (2025-12-24)
  → 'github:vicinaehq/vicinae/68faea42c62862614e071cee329486d907b3641a' (2025-12-28)

Running GitHub Actions on this PR

GitHub Actions will not run workflows on pull requests which are opened by a GitHub Action.

To run GitHub Actions workflows on this PR, close and re-open this pull request.

[mergify]

Merge Queue Status

🚫 The pull request has left the queue (rule: default) at 48a6177

This pull request spent 20 seconds in the queue, including 2 seconds running CI.
The checks were run on draft #239.

Required conditions to merge

• #approved-reviews-by>=1
  • Update flake/home-manager/flake.lock #232
• #check-failure==0
• #commits-behind <= 10
  • Update flake/home-manager/flake.lock #232
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Update flake/home-manager/flake.lock #232

Reason

Pull request #232 has been dequeued, merge conditions unmatch:

• #approved-reviews-by>=1
• #check-failure==0
• #commits-behind <= 10
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

Merge Queue Status

🚫 The pull request has left the queue (rule: default) at db9de2b

This pull request spent 13 seconds in the queue, including 1 second running CI.
The checks were run on draft #247.

Required conditions to merge

• #approved-reviews-by>=1
  • Update flake/home-manager/flake.lock #232
• #check-failure==0
• #commits-behind <= 10
  • Update flake/home-manager/flake.lock #232
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Update flake/home-manager/flake.lock #232

Reason

Pull request #232 has been dequeued, merge conditions unmatch:

• #approved-reviews-by>=1
• #check-failure==0
• #commits-behind <= 10
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

Merge Queue Status

🚫 The pull request has left the queue (rule: default) at 6fc6d30

This pull request spent 2 minutes 28 seconds in the queue, including 25 seconds running CI.
The checks were run on draft #261.

Required conditions to merge

• #approved-reviews-by>=1
  • Update flake/home-manager/flake.lock #232
• #check-failure==0
• #commits-behind <= 10
  • Update flake/home-manager/flake.lock #232
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Update flake/home-manager/flake.lock #232

Reason

Pull request #232 has been dequeued, merge conditions unmatch:

• #approved-reviews-by>=1
• #check-failure==0
• #commits-behind <= 10
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

Merge Queue Status

🚫 The pull request has left the queue (rule: default) at 2ff9c30

This pull request spent 42 seconds in the queue, including 11 seconds running CI.
The checks were run on draft #284.

Required conditions to merge

• #approved-reviews-by>=1
  • Update flake/home-manager/flake.lock #232
• #check-failure==0
• #commits-behind <= 10
  • Update flake/home-manager/flake.lock #232
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Update flake/home-manager/flake.lock #232

Reason

Pull request #232 has been dequeued, merge conditions unmatch:

• #approved-reviews-by>=1
• #check-failure==0
• #commits-behind <= 10
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for bc303f1.

🟢 All jobs passed!

But CI Insights is watching 👀

[mergify]

Merge Queue Status

🚫 The pull request has left the queue (rule: default) at bc303f1

This pull request spent 2 minutes 44 seconds in the queue, including 39 seconds running CI.
The checks were run on draft #298.

Required conditions to merge

• #approved-reviews-by>=1
  • Update flake/home-manager/flake.lock #232
• #check-failure==0
• #commits-behind <= 10
  • Update flake/home-manager/flake.lock #232
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Update flake/home-manager/flake.lock #232

Reason

Pull request #232 has been dequeued, merge conditions unmatch:

• #approved-reviews-by>=1
• #check-failure==0
• #commits-behind <= 10
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.