Lock file maintenance

[KubeArchitectBot]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 4am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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 has been generated by Mend Renovate.

[railway-app]

This PR was not deployed automatically as @KubeArchitectBot does not have access to the Railway project.

In order to get automatic PR deploys, please add @KubeArchitectBot to your workspace on Railway.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	leaflock	60504ff	Dec 08 2025, 12:54 AM

[github-actions]

❌MegaLinter analysis: Error

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
❌ BASH	shellcheck	10		1	1	0.84s
✅ DOCKERFILE	hadolint	3		0	0	0.36s
✅ JSON	jsonlint	18		0	0	0.55s
✅ MARKDOWN	markdownlint	33	2	0	0	2.84s
✅ REPOSITORY	secretlint	yes		no	no	6.93s
⚠️ SQL	sqlfluff	2	0	1	0	5.32s
✅ YAML	yamllint	51		0	0	5.67s

Detailed Issues

❌ BASH / shellcheck - 1 error

warning: In POSIX sh, string indexing is undefined.
    ┌─ frontend/docker-entrypoint.sh:219:49
    │
219 │     log "✅ Injected VITE_CLERK_PUBLISHABLE_KEY (${VITE_CLERK_PUBLISHABLE_KEY:0:20}...)"
    │                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    │
    = SC3057
    = For more information: https://www.shellcheck.net/wiki/SC3057

warning: 1 warnings emitted

⚠️ SQL / sqlfluff - 1 error

WARNING: Config file .github/linters/.sqlfluff set a deprecated config value `rules:max_line_length`. This will be removed in a later release. This has been mapped to `max_line_length` set to a value of 120 for this run. Please update your configuration to remove this warning. 

The max_line_length config has moved from sqlfluff:rules to the root sqlfluff level.

See https://docs.sqlfluff.com/en/stable/perma/configuration.html for more details.

==== finding fixable violations ====
WARNING    Rule configuration contain a section for unexpected rule 'L010'. These values will be ignored. 
WARNING    The reference was however found as a match for rule CP01 with name 'capitalisation.keywords'. SQLFluff assumes configuration for this rule will be specified in 'sqlfluff:rules:capitalisation.keywords'. 
WARNING    Rule configuration contain a section for unexpected rule 'L014'. These values will be ignored. 
WARNING    The reference was however found as a match for rule CP02 with name 'capitalisation.identifiers'. SQLFluff assumes configuration for this rule will be specified in 'sqlfluff:rules:capitalisation.identifiers'. 
WARNING    Rule configuration contain a section for unexpected rule 'L030'. These values will be ignored. 
WARNING    The reference was however found as a match for rule CP03 with name 'capitalisation.functions'. SQLFluff assumes configuration for this rule will be specified in 'sqlfluff:rules:capitalisation.functions'. 
== [backend/config/postgres_security.sql] FAIL
L:   5 | P:   1 |  PRS | Line 5, Position 1: Found unparsable section: 'ALTER
                       | SYSTEM SET ssl = on;\nALTER SYSTEM ...'
WARNING    Rule configuration contain a section for unexpected rule 'L010'. These values will be ignored. 
WARNING    The reference was however found as a match for rule CP01 with name 'capitalisation.keywords'. SQLFluff assumes configuration for this rule will be specified in 'sqlfluff:rules:capitalisation.keywords'. 
WARNING    Rule configuration contain a section for unexpected rule 'L014'. These values will be ignored. 
WARNING    The reference was however found as a match for rule CP02 with name 'capitalisation.identifiers'. SQLFluff assumes configuration for this rule will be specified in 'sqlfluff:rules:capitalisation.identifiers'. 
WARNING    Rule configuration contain a section for unexpected rule 'L030'. These values will be ignored. 
WARNING    The reference was however found as a match for rule CP03 with name 'capitalisation.functions'. SQLFluff assumes configuration for this rule will be specified in 'sqlfluff:rules:capitalisation.functions'. 
==== no fixable linting violations found ====
All Finished!
==== lint for unfixable violations ====
== [backend/config/postgres_security.sql] PASS
== [backend/scripts/reset-mfa.sql] PASS

See detailed reports in MegaLinter artifacts

You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:

• oxsecurity/megalinter/flavors/documentation@v9.2.0 (49 linters)
• oxsecurity/megalinter/flavors/ruby@v9.2.0 (50 linters)
• oxsecurity/megalinter/flavors/rust@v9.2.0 (50 linters)

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@9.2.0 --custom-flavor-setup --custom-flavor-linters BASH_SHELLCHECK,DOCKERFILE_HADOLINT,JSON_JSONLINT,MARKDOWN_MARKDOWNLINT,REPOSITORY_SECRETLINT,SQL_SQLFLUFF,YAML_YAMLLINT