chore: sync with WeblateOrg/meta

.github/workflows/pre-commit.yml

@@ -13,6 +13,8 @@ on:
     - codex/**
     - renovate/**
     - weblate
+    - weblate-*
+    - weblate/**
     - dependabot/**
   pull_request:
 

SECURITY.md

@@ -8,22 +8,18 @@ This file is maintained in https://github.com/WeblateOrg/meta/
 
 # Weblate security
 
-The Weblate team takes security and related transparency very seriously.
-We welcome any peer review of our 100% open-source code to ensure nobody's Weblate
-is ever compromised or hacked.
+If you believe you have found a security vulnerability in a Weblate project,
+**do not open a public issue**. Report it privately by emailing
+[security@weblate.org](mailto:security@weblate.org) or selecting
+**Security → Report a vulnerability** in this repository.
 
-If you think you have identified a security issue with a Weblate project, **do
-not open a public issue**.
+Please describe the issue, affected versions, and steps to reproduce it, if
+known.
 
-To responsibly report a security issue, please navigate to the Security tab for
-the repository and click “Report a vulnerability”.
+For security scope and assumptions, consult this repository's threat model if
+it has one, or the [Weblate threat model][threat-model] for the main application.
+The [security documentation][reporting] explains the full reporting and
+disclosure process.
 
-Be sure to include as much detail as necessary in your report. As with
-reporting normal issues, a minimal reproducible example will help the
-maintainers address the issue faster.
-
-More information about practices for reporting and fixing security issues is
-described in [our documentation][1]. This ensures all vulnerabilities are
-solved securely, quickly, and transparently.
-
-[1]: https://docs.weblate.org/en/latest/security/issues.html
+[threat-model]: https://docs.weblate.org/en/latest/security/threat-model.html
+[reporting]: https://docs.weblate.org/en/latest/security/issues.html