Matrix Docker Ansible eploy
Nie możesz wybrać więcej, niż 25 tematów Tematy muszą się zaczynać od litery lub cyfry, mogą zawierać myślniki ('-') i mogą mieć do 35 znaków.
 
 
 

94 wiersze
3.6 KiB

  1. {
  2. "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  3. "extends": [
  4. "config:recommended",
  5. "helpers:pinGitHubActionDigests"
  6. ],
  7. "labels": [
  8. "dependencies"
  9. ],
  10. "customManagers": [
  11. {
  12. "customType": "regex",
  13. "managerFilePatterns": [
  14. "/defaults/main.yml$/"
  15. ],
  16. "matchStrings": [
  17. "# renovate: datasource=(?<datasource>[a-z-.]+?) depName=(?<depName>[^\\s]+?)(?: (?:lookupName|packageName)=(?<packageName>[^\\s]+?))?(?: versioning=(?<versioning>[a-z-0-9]+?))?\\s+[A-Za-z0-9_]+?(?:_version|_tag)\\s*:\\s*[\"']?(?<currentValue>.+?)[\"']?\\s"
  18. ]
  19. },
  20. {
  21. "description": "Helper container images used by the Molecule scenarios. They are pinned once in molecule-shared/vars.yml rather than inline in each role's verify.yml, so this manager keeps that single pin current.",
  22. "customType": "regex",
  23. "managerFilePatterns": [
  24. "/^molecule-shared/vars\\.yml$/"
  25. ],
  26. "matchStrings": [
  27. "# renovate: datasource=(?<datasource>[a-z-.]+?) depName=(?<depName>[^\\s]+?)\\s+[A-Za-z0-9_]+?\\s*:\\s*[\"'][^:]+:(?<currentValue>[^\"']+)[\"']"
  28. ]
  29. }
  30. ],
  31. "packageRules": [
  32. {
  33. "ignoreUnstable": false,
  34. "versioning": "loose",
  35. "matchSourceUrls": [
  36. "https://github.com/devture/com.devture.ansible.role{/,}**",
  37. "https://github.com/mother-of-all-self-hosting{/,}**"
  38. ]
  39. },
  40. {
  41. "description": "mautrix images are dual-tagged (v0.YYMM.PATCH and vYY.MM[.PATCH]). Stick to the v0 scheme: it matches the git tags (needed for self-building) and has a consistent number of components (the calver tags do not, which makes Renovate stop offering updates).",
  42. "matchPackageNames": [
  43. "dock.mau.dev/mautrix/**"
  44. ],
  45. "allowedVersions": "/^v0\\./"
  46. },
  47. {
  48. "description": "Automerge version bumps of roles maintained in the MASH organization and of devture roles (via branch push - no PR)",
  49. "matchManagers": [
  50. "ansible-galaxy"
  51. ],
  52. "matchSourceUrls": [
  53. "https://github.com/devture/com.devture.ansible.role{/,}**",
  54. "https://github.com/mother-of-all-self-hosting{/,}**"
  55. ],
  56. "automerge": true,
  57. "automergeType": "branch"
  58. },
  59. {
  60. "description": "Housekeeping updates merge via branch push (no PR, no email); a failure on the branch still surfaces as a PR. i18n/requirements.txt bumps are exercised by the Matrix i18n workflow before merging.",
  61. "matchFileNames": [
  62. ".github/workflows/close-stale-issues.yml",
  63. ".github/workflows/i18n.yml",
  64. ".github/workflows/lock-threads.yml",
  65. ".github/workflows/matrix.yml",
  66. ".github/workflows/update-translations.yml",
  67. "flake.lock",
  68. "i18n/requirements.txt",
  69. "mise.toml"
  70. ],
  71. "automerge": true,
  72. "automergeType": "branch"
  73. },
  74. {
  75. "description": "Molecule's own dependencies merge via branch push (no PR, no email). Anything under molecule-shared/ - the helper container images, Postgres, and the Python pins - triggers the Molecule workflow, and a change to a shared file makes it run every scenario, so an update only merges once the whole suite has passed on it. A failure surfaces as a PR instead. This is how a new Postgres major reaches us: the bump runs every scenario against it before anything is merged.",
  76. "matchFileNames": [
  77. "molecule-shared/**",
  78. ".github/workflows/molecule.yml"
  79. ],
  80. "automerge": true,
  81. "automergeType": "branch"
  82. }
  83. ],
  84. "pre-commit": {
  85. "enabled": true
  86. },
  87. "nix": {
  88. "enabled": true,
  89. "lockFileMaintenance": {
  90. "enabled": true
  91. }
  92. }
  93. }