chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
bitnami/metallb-controller (source)		patch	0.14.5-debian-12-r7 -> 0.14.9-debian-12-r0
bitnami/metallb-speaker (source)		patch	0.14.5-debian-12-r7 -> 0.14.9-debian-12-r0
bitnami/postgresql (source)		minor	14.12.0-debian-12-r15 -> 14.15.0-debian-12-r6
bitnami/postgresql (source)		minor	16.3.0-debian-12-r17 -> 16.6.0-debian-12-r2
cert-manager (source)		minor	v1.15.1 -> v1.16.2
external-dns (source)		minor	8.0.0 -> 8.7.1
fluxcd/flux2	Kustomization	minor	v2.3.0 -> v2.4.0
fluxcd/flux2		minor	v2.3.0 -> v2.4.0
ghcr.io/mealie-recipes/mealie		minor	v1.11.0 -> v1.12.0
ghcr.io/paperless-ngx/paperless-ngx		minor	2.10.2 -> 2.13.5
immich (source)		minor	0.7.1 -> 0.9.0
metallb (source)		minor	6.3.5 -> 6.4.2
metrics-server (source)		minor	7.2.6 -> 7.3.0
nginx		patch	1.27.0-alpine -> 1.27.3-alpine
photoprism (source)		patch	7.4.14 -> 7.4.19
redis		minor	7.2 -> 7.4

---

Release Notes

cert-manager/cert-manager (cert-manager)

v1.16.2

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

This patch release of cert-manager 1.16 makes several changes to how PEM input is validated, adding maximum sizes appropriate to the type of PEM data which is being parsed.

This is to prevent an unacceptable slow-down in parsing specially crafted PEM data. The issue was found by Google's OSS-Fuzz project.

The issue is low severity; to exploit the PEM issue would require privileged access which would likely allow Denial-of-Service through other methods.

Note also that since most PEM data parsed by cert-manager comes from ConfigMap or Secret resources which have a max size limit of approximately 1MB, it's difficult to force cert-manager to parse large amounts of PEM data.

Further information is available in GHSA-r4pg-vg54-wxx4

In addition, the version of Go used to build cert-manager 1.16 was updated along with the base images.

Changes by Kind

Bug or Regression

• Set a maximum size for PEM inputs which cert-manager will accept to remove possibility of taking a long time to process an input (#​7401, @​SgtCoDFish)

Other (Cleanup or Flake)

• Bump go to 1.23.3 and bump base images to latest available (#​7431, @​SgtCoDFish)

v1.16.1

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

The cert-manager 1.16 release includes: new Helm chart features, more Prometheus metrics, memory optimizations, and various improvements and bug fixes for the ACME issuer and Venafi Issuer.

📖 Read the complete 1.16 release notes before upgrading.

📜Changes since v1.16.0

Bug or Regression

• BUGFIX: Helm schema validation: the new schema validation was too strict for the "global" section. Since the global section is shared across all charts and sub-charts, we must also allow unknown fields. (#​7348, @inteon)
• BUGFIX: Helm will now accept percentages for the podDisruptionBudget.minAvailable and podDisruptionBudget.maxAvailable values. (#​7345, @inteon)
• Helm: allow enabled to be set as a value to toggle cert-manager as a dependency. (#​7356, @inteon)
• BUGFIX: A change in v1.16.0 caused cert-manager's ACME ClusterIssuer to look in the wrong namespace for resources required for the issuance (e.g. credential Secrets). This is now fixed in v1.16.1. (#​7342, @inteon)

v1.16.0

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

The cert-manager 1.16 release includes: new Helm chart features, more Prometheus metrics, memory optimizations, and various improvements and bug fixes for the ACME issuer and Venafi Issuer.

📖 Read the complete 1.16 release notes at cert-manager.io.

⚠️ Known issues

1. Helm Chart: JSON schema prevents the chart being used as a sub-chart on Rancher RKE.
2. ACME DNS01 ClusterIssuer fail while loading credentials from Secret resources.

❗ Breaking changes

1. Helm schema validation may reject your existing Helm values files if they contain typos or unrecognized fields.
2. Venafi Issuer may fail to renew certificates if the requested duration conflicts with the CA’s minimum or maximum policy settings in Venafi.
3. Venafi Issuer may fail to renew Certificates if the issuer has been configured for TPP with username-password authentication.

📖 Read the complete 1.16 release notes at cert-manager.io.

📜 Changes since v1.15.0

📖 Read the complete 1.16 release notes at cert-manager.io.

Feature

• Add SecretRef support for Venafi TPP issuer CA Bundle (#​7036, @sankalp-at-gh)
• Add renewBeforePercentage alternative to renewBefore (#​6987, @cbroglie)
• Add a metrics server to the cainjector (#​7194, @wallrj)
• Add a metrics server to the webhook (#​7182, @wallrj)
• Add client certificate auth method for Vault issuer (#​4330, @joshmue)
• Add process and go runtime metrics for controller (#​6966, @mindw)
• Added app.kubernetes.io/managed-by: cert-manager label to the cert-manager-webhook-ca Secret (#​7154, @jrcichra)
• Allow the user to specify a Pod template when using GatewayAPI HTTP01 solver, this mirrors the behavior when using the Ingress HTTP01 solver. (#​7211, @ThatsMrTalbot)
• Create token request RBAC for the cert-manager ServiceAccount by default (#​7213, @Jasper-Ben)
• Feature: Append cert-manager user-agent string to all AWS API requests, including IMDS and STS requests. (#​7295, @wallrj)
• Feature: Log AWS SDK warnings and API requests at cert-manager debug level to help debug AWS Route53 problems in the field. (#​7292, @wallrj)
• Feature: The Route53 DNS solver of the ACME Issuer will now use regional STS endpoints computed from the region that is supplied in the Issuer spec or in the AWS_REGION environment variable.
  Feature: The Route53 DNS solver of the ACME Issuer now uses the "ambient" region (AWS_REGION or AWS_DEFAULT_REGION) if issuer.spec.acme.solvers.dns01.route53.region is empty; regardless of the flags --issuer-ambient-credentials and --cluster-issuer-ambient-credentials. (#​7299, @wallrj)
• Helm: adds JSON schema validation for the Helm values. (#​7069, @inteon)
• If the --controllers flag only specifies disabled controllers, the default controllers are now enabled implicitly.
  Added disableAutoApproval and approveSignerNames Helm chart options. (#​7049, @inteon)
• Make it easier to configure cert-manager using Helm by defaulting config.apiVersion and config.kind within the Helm chart. (#​7126, @ThatsMrTalbot)
• Now passes down specified duration to Venafi client instead of using the CA default only. (#​7104, @Guitarkalle)
• Reduce the memory usage of cainjector, by only caching the metadata of Secret resources.
  Reduce the load on the K8S API server when cainjector starts up, by only listing the metadata of Secret resources. (#​7161, @wallrj)
• The Route53 DNS01 solver of the ACME Issuer can now detect the AWS region from the AWS_REGION and AWS_DEFAULT_REGION environment variables, which is set by the IAM for Service Accounts (IRSA) webhook and by the Pod Identity webhook.
  The issuer.spec.acme.solvers.dns01.route53.region field is now optional.
  The API documentation of the region field has been updated to explain when and how the region value is used. (#​7287, @wallrj)
• Venafi TPP issuer can now be used with a username & password combination with OAuth. Fixes #​4653.
  Breaking: cert-manager will no longer use the API Key authentication method which was deprecated in 20.2 and since removed in 24.1 of TPP. (#​7084, @hawksight)
• You can now configure the pod security context of HTTP-01 solver pods. (#​5373, @aidy)
• Helm: New value webhook.extraEnv, allows you to set custom environment variables in the webhook Pod.
  Helm: New value cainjector.extraEnv, allows you to set custom environment variables in the cainjector Pod.
  Helm: New value startupapicheck.extraEnv, allows you to set custom environment variables in the startupapicheck Pod. (#​7319, @wallrj)

Bug or Regression

• Adds support (behind a flag) to use a domain qualified finalizer. If the feature is enabled (which is not by default), it should prevent Kubernetes from reporting: metadata.finalizers: "finalizer.acme.cert-manager.io": prefer a domain-qualified finalizer name to avoid accidental conflicts with other finalizer writers (#​7273, @jsoref)
• BUGFIX Route53: explicitly set the aws-global STS region which is now required by the github.com/aws/aws-sdk-go-v2 library. (#​7108, @inteon)
• BUGFIX: fix issue that caused Vault issuer to not retry signing when an error was encountered. (#​7105, @inteon)
• BUGFIX: the dynamic certificate source used by the webhook TLS server failed to detect a root CA approaching expiration, due to a calculation error. This will cause the webhook TLS server to fail renewing its CA certificate. Please upgrade before the expiration of this CA certificate is reached. (#​7230, @inteon)
• Bugfix: Prevent aggressive Route53 retries caused by IRSA authentication failures by removing the Amazon Request ID from errors wrapped by the default credential cache. (#​7291, @wallrj)
• Bugfix: Prevent aggressive Route53 retries caused by STS authentication failures by removing the Amazon Request ID from STS errors. (#​7259, @wallrj)
• Bump grpc-go to fix GHSA-xr7q-jx4m-x55m (#​7164, @SgtCoDFish)
• Bump the go-retryablehttp dependency to fix CVE-2024-6104 (#​7125, @SgtCoDFish)
• Fix Azure DNS causing panics whenever authentication error happens (#​7177, @eplightning)
• Fix incorrect indentation of endpointAdditionalProperties in the PodMonitor template of the Helm chart (#​7190, @wallrj)
• Fixes ACME HTTP01 challenge behavior when using Gateway API to prevent unbounded creation of HTTPRoute resources (#​7178, @miguelvr)
• Handle errors arising from challenges missing from the ACME server (#​7202, @bdols)
• Helm BUGFIX: the cainjector ConfigMap was not mounted in the cainjector deployment. (#​7052, @inteon)
• Improve the startupapicheck: validate that the validating and mutating webhooks are doing their job. (#​7057, @inteon)
• The KeyUsages X.509 extension is no longer added when there are no key usages set (in accordance to RFC 5280 Section 4.2.1.3) (#​7250, @inteon)
• Update github.com/Azure/azure-sdk-for-go/sdk/azidentity to address CVE-2024-35255 (#​7087, @dependabot[bot])

Other (Cleanup or Flake)

• Old API versions were removed from the codebase.
  Removed:
  (acme.)cert-manager.io/v1alpha2
  (acme.)cert-manager.io/v1alpha3
  (acme.)cert-manager.io/v1beta1 (#​7278, @inteon)
• Upgrading to client-go v0.31.0 removes a lot of noisy reflector.go: unable to sync list result: internal error: cannot cast object DeletedFinalStateUnknown errors from logs. (#​7237, @inteon)
• Bump Go to v1.23.2 (#​7324, @cert-manager-bot)

v1.15.4

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

This patch release of cert-manager 1.15 makes several changes to how PEM input is validated, adding maximum sizes appropriate to the type of PEM data which is being parsed.

This is to prevent an unacceptable slow-down in parsing specially crafted PEM data. The issue was found by Google's OSS-Fuzz project.

The issue is low severity; to exploit the PEM issue would require privileged access which would likely allow Denial-of-Service through other methods.

Note also that since most PEM data parsed by cert-manager comes from ConfigMap or Secret resources which have a max size limit of approximately 1MB, it's difficult to force cert-manager to parse large amounts of PEM data.

Further information is available in GHSA-r4pg-vg54-wxx4

In addition, the version of Go used to build cert-manager 1.15 was updated along with the base images, and a Route53 bug fix was backported.

Changes by Kind

Bug or Regression

• Bugfix: Prevent aggressive Route53 retries caused by STS authentication failures by removing the Amazon Request ID from STS errors. (#​7261, @​cert-manager-bot)
• Set a maximum size for PEM inputs which cert-manager will accept to remove possibility of taking a long time to process an input (#​7402, @​SgtCoDFish)

Other (Cleanup or Flake)

• Bump go to 1.22.9 (#​7424, @​SgtCoDFish)
• Upgrade Go to 1.22.8, the latest available patch release (#​7406, @​SgtCoDFish)

v1.15.3

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

🔗 See v1.15.0 for more information about cert-manager 1.15 and read-before-upgrade info.

📜 Changes since v1.15.2

Bug or Regression

• BUGFIX: the dynamic certificate source used by the webhook TLS server failed to detect a root CA approaching expiration, due to a calculation error. This will cause the webhook TLS server to fail renewing its CA certificate. Please upgrade before the expiration of this CA certificate is reached. (#​7232, @​cert-manager-bot)

v1.15.2

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

🔗 See v1.15.0 for more information about cert-manager 1.15 and read-before-upgrade info.

📜 Changes since v1.15.1

Bug or Regression

• BUGFIX route53: explicitly set the aws-global STS region which is now required by the github.com/aws/aws-sdk-go-v2 library. (#​7189, @cert-manager-bot)
• Bump grpc-go to fix GHSA-xr7q-jx4m-x55m (#​7167, @SgtCoDFish)
• Fix Azure DNS causing panics whenever authentication error happens (#​7188, @cert-manager-bot)
• Fix incorrect value and indentation of endpointAdditionalProperties in the PodMonitor template of the Helm chart (#​7191, @inteon)
• Fixes ACME HTTP01 challenge behavior when using Gateway API to prevent unbounded creation of HTTPRoute resources (#​7186, @cert-manager-bot)
• Upgrade golang from 1.22.3 to 1.22.5 (#​7165, @github-actions)

bitnami/charts (external-dns)

v8.7.1

• [bitnami/external-dns] Release 8.7.1 (#​31120)

v8.7.0

• [bitnami/external-dns] Detect non-standard images (#​30894)

v8.6.1

• [bitnami/external-dns] Release 8.6.1 (#​30747)

v8.6.0

• [bitnami/external-dns] feat: add support to namespaceOverride and simplify name helpers (#​30515)

v8.5.1

• [bitnami/external-dns] Release 8.5.1 (#​30262)

v8.5.0

• [bitnami/external-dns] Add targetLabels option to ServiceMonitor (#​29828) (bba5754), closes #​29828 #​29332

v8.4.0

• [bitnami/external-dns] add support for multiple rfc2136 zones (#​30011) (174879d), closes #​30011

v8.3.12

• [bitnami/external-dns] Allow rfc2136-zone to specify multiple zones (#​28681)

v8.3.11

• [bitnami/*] Remove wrong comment about imagePullPolicy (#​30107) (a51f9e4), closes #​30107
• [bitnami/external-dns] fix: secret not getting created when pihole password value is set (#​30114) (15c8fa0), closes #​30114

v8.3.10

• [bitnami/external-dns] chore: 🔧 👷 Re-enable CRD automation (#​29266) (9e50d55), closes #​29266
• Update documentation links to techdocs.broadcom.com (#​29931) (f0d9ad7), closes #​29931

v8.3.9

• [bitnami/external-dns] Release 8.3.9 (#​29690)

v8.3.8

• [bitnami/external-dns] Fixed oci workload identity secret creation (#​29374)

v8.3.7

• [bitnami/external-dns] Release 8.3.7 (#​29231)

v8.3.6

• [bitnami/external-dns] Release 8.3.6 (#​29211) (bcab075), closes #​29211

v8.3.5

• [bitnami/external-dns] Fix crd.create=true (#​27434)

v8.3.4

• [bitnami/external-dns] Release 8.3.4 (#​28711)

v8.3.3

• [bitnami/external-dns] Release 8.3.3 (#​28422)

v8.3.2

• [bitnami/external-dns] Release 8.3.2 (#​28315) (25da286), closes #​28315

v8.3.1

• [bitnami/external-dns] Release 8.3.1 (#​28245) (4ab8fdf), closes #​28245

v8.3.0

• [bitnami/external-dns] feat: Add support for provider scaleway secretName (#​24630) (fdb8c86), closes #​24630

v8.2.3

• [bitnami/external-dns] Add value.yaml support for "--infoblox-create-ptr" argument flag (#​27882)

v8.2.2

• [bitnami/external-dns] add revisionHistoryLimit value (#​27913) (8cd1824), closes #​27913

v8.2.1

• [bitnami/external-dns] docs: update registry doc url (#​27505) (cf18b0b), closes #​27505

v8.2.0

• [bitnami/external-dns] Added extra arguments for Traefik new/legacy resource support (#​27766) (31ff6e7), closes #​27766

v8.1.0

• [bitnami/external-dns] add default pihole.password value (#​27158) (531123b), closes #​27158

v8.0.2

• [bitnami/external-dns] Release 8.0.2 (#​27760) (565db6a), closes #​27760

v8.0.1

• [bitnami/*] Update README changing TAC wording (#​27530) (52dfed6), closes #​27530
• [bitnami/external-dns] Release 8.0.1 (#​27645) (ca9be4a), closes #​27645

fluxcd/flux2 (fluxcd/flux2)

v2.4.0

Compare Source

Highlights

Flux v2.4.0 is a feature release. Users are encouraged to upgrade for the best experience.

For a comprehensive overview of new features and API changes included in this release, please refer to the Announcing Flux 2.4 GA blog post.

This release marks the General Availability (GA) of Flux Bucket API. The Bucket v1 API comes with new features including: proxy support, mTLS and custom STS configuration for AWS S3 and MinIO LDAP authentication.

The GitRepository v1 API gains support for OIDC authentication. Starting with this version, you can authenticate against Azure DevOps repositories using AKS Workload Identity.

The OCIRepository v1beta2 API gains support for proxy configuration thus allowing dedicated HTTP/S Proxy authentication on multi-tenant Kubernetes clusters.

The HelmRelease v2 API gains support for disabling JSON schema validation of the Helm release values during installation and upgrade. And allows adopting existing Kubernetes resources during Helm release installation.

The Flux controllers are now built with Go 1.23 and their dependencies have been updated to Kubernetes 1.31, Helm 3.16, SOPS 3.9 Cosign 2.4 and Notation 1.2.

❤️ Big thanks to all the Flux contributors that helped us with this release!

Kubernetes compatibility

This release is compatible with the following Kubernetes versions:

Kubernetes version	Minimum required
v1.29	>= 1.29.0
v1.30	>= 1.30.0
v1.31	>= 1.31.0

[!NOTE]
Note that the Flux project offers support only for the latest three minor versions of Kubernetes.
Backwards compatibility with older versions of Kubernetes and OpenShift is offered by vendors such as
ControlPlane that provide enterprise support for Flux.

OpenShift compatibility

Flux can be installed on Red Hat OpenShift cluster directly from OperatorHub using Flux Operator.
The operator allows the configuration of Flux multi-tenancy lockdown, network policies, persistent storage, sharding, vertical scaling and the synchronization of the cluster state from Git repositories, OCI artifacts and S3-compatible storage.

API changes

Bucket v1

The Bucket kind was promoted from v1beta2 to v1 (GA).

The v1 API is backwards compatible with v1beta2.

New fields:

• .spec.proxySecretRef allows configuring HTTP/S Proxy authentication for the S3-compatible storage service.
• .spec.certSecretRef allows custom TLS client certificate and CA for secure communication with the S3-compatible storage service.
• .spec.sts allows custom STS configuration for AWS S3 and MinIO LDAP authentication.

GitRepository v1

The GitRepository kind gains new optional fields with no breaking changes.

New fields:

• .spec.provider allows specifying an OIDC provider used for authentication purposes. Currently, only the azure provider is supported.

OCIRepository v1beta2

The OCIRepository kind gains new optional fields with no breaking changes.

New fields:

• .spec.proxySecretRef allows configuring HTTP/S Proxy authentication for the container registry service.

HelmRelease v2

The HelmRelease kind gains new optional fields with no breaking changes.

New fields:

• .spec.install.disableSchemaValidation allows disabling the JSON schema validation of the Helm release values during installation.
• .spec.upgrade.disableSchemaValidation allows disabling the JSON schema validation of the Helm release values during upgrade.

Upgrade procedure

Upgrade Flux from v2.3.0 to v2.4.0 either by rerunning bootstrap or by using the Flux GitHub Action.

To upgrade the APIs, make sure the new CRDs and controllers are deployed, and then change the manifests in Git:

1. Set apiVersion: source.toolkit.fluxcd.io/v1 in the YAML files that contain Bucket definitions.
2. Commit, push and reconcile the API version changes.

Bumping the APIs version in manifests can be done gradually.
It is advised to not delay this procedure as the deprecated versions will be removed after 6 months.

Components changelog

• source-controller v1.4.0 v1.4.1
• kustomize-controller v1.4.0
• notification-controller v1.4.0
• helm-controller v1.1.0
• image-reflector-controller v0.33.0
• image-automation-controller v0.39.0

New Documentation

• Bucket v1 specification
• Azure DevOps OIDC auth configuration

CLI Changelog

• PR #​5014 - @​stefanprodan - Update Kubernetes dependencies to v1.31.1
• PR #​5011 - @​stefanprodan - Remove TLS deprecated flags from flux create secret
• PR #​5010 - @​stefanprodan - Add flux create secret proxy command
• PR #​5009 - @​stefanprodan - Add --proxy-secret-ref to flux create source commands
• PR #​5008 - @​stefanprodan - Promote bucket commands to GA
• PR #​5007 - @​stefanprodan - Run conformance tests for Kubernetes 1.29-1.31
• PR #​5005 - @​fluxcdbot - Update toolkit components
• PR #​5004 - @​fluxcdbot - Update source-controller to v1.4.1
• PR #​4986 - @​dipti-pai - [RFC-0007] Add --provider flag to flux create source git
• PR #​4970 - @​JasonTheDeveloper - Update notaryproject/notation-go to 1.2.1
• PR #​4967 - @​mxtw - tests: use tempdir to avoid manual gc
• PR #​4959 - @​stefanprodan - Fix GitHub bootstrap for repositories with custom properties
• PR #​4948 - @​harshitasao - fix: fixed GHA token-permission and pinned dependencies issue
• PR #​4939 - @​bkreitch - Recursively diff Kustomizations
• PR #​4936 - @​stefanprodan - Build with Go 1.23
• PR #​4934 - @​stefanprodan - Update dependencies to Kubernetes v1.31.0
• PR #​4922 - @​bkreitch - Stop spinner on cancel of flux diff kustomization
• PR #​4918 - @​matheuscscp - Fix reconcile helmrelease command description
• PR #​4892 - @​stefanprodan - Run conformance tests for Kubernetes v1.31
• PR #​4871 - @​harshitasao - changed the scorecard badge link to the standard format
• PR #​4866 - @​nagyv - Introduce visibility flag for bootstrap gitlab
• PR #​4863 - @​stefanprodan - Update conformance tests to Kubernetes v1.30.2
• PR #​4845 - @​stefanprodan - Run ARM64 e2e tests on GitHub runners
• PR #​4842 - @​stefanprodan - Add part-of label to controllers base
• PR #​4835 - @​stefanprodan - ci: Adapt config to GoRelease v2
• PR #​4806 - @​dipti-pai - [RFC] Passwordless authentication for Git repositories

mealie-recipes/mealie (ghcr.io/mealie-recipes/mealie)

v1.12.0: - Image import via OpenAI

Compare Source

Highlights

• Import recipes via an image, using OpenAI. https://github.com/mealie-recipes/mealie/pull/3974

What's Changed

• feat: Added fr-BE by @​TheSuperBeaver in https://github.com/mealie-recipes/mealie/pull/4004
• feat: If there's only one shopping list, navigate directly to it by @​boc-the-git in https://github.com/mealie-recipes/mealie/pull/3958
• feat: Import + Translate recipe images with OpenAI by @​michael-genson in https://github.com/mealie-recipes/mealie/pull/3974
• feat: Seed support for plural units by @​Choromanski in https://github.com/mealie-recipes/mealie/pull/3933
• fix: recipe clean_time function missing translator argument on recursion by @​Kuchenpirat in https://github.com/mealie-recipes/mealie/pull/3969
• fix: Make recipe scraper cleaner more fault tolerant by @​michael-genson in https://github.com/mealie-recipes/mealie/pull/3967
• fix: Bump tzdata 2024.1 by @​michael-genson in https://github.com/mealie-recipes/mealie/pull/3993
• fix: Don't load from secrets dir if nonexistent or inaccessible by @​anoadragon453 in https://github.com/mealie-recipes/mealie/pull/4002
• fix: Lint Python code with ruff by @​cclauss in https://github.com/mealie-recipes/mealie/pull/3799
• fix(auto): Update pre-commit hooks by @​github-actions in https://github.com/mealie-recipes/mealie/pull/3987
• fix(auto): Update pre-commit hooks by @​github-actions in https://github.com/mealie-recipes/mealie/pull/4020
• fix(auto): Update pre-commit hooks by @​github-actions in https://github.com/mealie-recipes/mealie/pull/4052
• docs(auto): Update image tag, for release v1.11.0 by @​github-actions in https://github.com/mealie-recipes/mealie/pull/3965
• docs: update home-assistant.md by @​eltociear in https://github.com/mealie-recipes/mealie/pull/4049
• docs: fix import bookmarklet trailing slashes by @​vahtos in https://github.com/mealie-recipes/mealie/pull/4057
• fix(deps): update dependency uvicorn to v0.30.4 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3971
• fix(deps): update dependency openai to v1.37.2 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3976
• fix(deps): update dependency pyjwt to v2.9.0 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3973
• fix(deps): update dependency openai to v1.38.0 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3981
• fix(deps): update dependency fastapi to ^0.112.0 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3977
• fix(deps): update dependency uvicorn to v0.30.5 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3979
• fix(deps): update dependency sqlalchemy to v2.0.32 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3988
• fix(deps): update dependency tzdata to v2024 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3990
• fix(deps): update dependency openai to v1.39.0 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3989
• fix(deps): update dependency openai to v1.40.0 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3994
• fix(deps): update dependency rapidfuzz to v3.9.6 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3997
• fix(deps): update dependency pyyaml to v6.0.2 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3996
• fix(deps): update dependency openai to v1.40.1 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4001
• fix(deps): update dependency openai to v1.40.2 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4008
• fix(deps): update dependency orjson to v3.10.7 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4009
• fix(deps): update dependency openai to v1.40.3 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4012
• fix(deps): update dependency lxml to v5.3.0 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4015
• fix(deps): update dependency uvicorn to v0.30.6 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4030
• fix(deps): update dependency openai to v1.40.6 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4023
• fix(deps): update dependency fastapi to v0.112.1 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4041
• fix(deps): update dependency openai to v1.41.0 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4042
• fix(deps): update dependency openai to v1.41.1 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4056
• fix(deps): update dependency openai to v1.42.0 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4060
• chore(deps): update dependency ruff to v0.5.6 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3980
• chore(deps): update dependency mkdocs-material to v9.5.31 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3978
• chore(deps): update dependency coverage to v7.6.1 by @​renovate in https://github.com/mealie-recipes/mealie/pull/3985
• chore(deps): update dependency ruff to v0.5.7 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4005
• chore(deps): update dependency ruff to ^0.6.0 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4039
• chore(deps): update dependency mkdocs-material to v9.5.32 by @​renovate in https://github.com/mealie-recipes/mealie/pull/4053
• New Crowdin updates (Total: 12)

New Contributors

• @​TheSuperBeaver made their first contribution in https://github.com/mealie-recipes/mealie/pull/4004
• @​vahtos made their first contribution in https://github.com/mealie-recipes/mealie/pull/4057

Full Changelog: mealie-recipes/mealie@v1.11.0...v1.12.0

paperless-ngx/paperless-ngx (ghcr.io/paperless-ngx/paperless-ngx)

v2.13.5: Paperless-ngx v2.13.5

Compare Source

paperless-ngx 2.13.5

Bug Fixes

• Fix: handle page count exception for pw-protected files @​shamoon (#​8240)
• Fix: correctly track task id in list for change detection @​shamoon (#​8230)
• Fix: Admin pages should show trashed documents @​stumpylog (#​8068)
• Fix: tag colors shouldn't change when selected in list @​shamoon (#​8225)
• Fix: fix re-activation of save button when changing array items @​shamoon (#​8208)
• Fix: fix thumbnail clipping, select inverted color in safari dark mode not system @​shamoon (#​8193)
• Fix: select checkbox should remain visible @​shamoon (#​8185)
• Fix: warn with proper error on ASN exists in trash @​shamoon ([#​8176](https://redirect.github.com/paperless-ngx/paperless-ng

---

Configuration

📅 Schedule: 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.