update-gitops-repository 2.0.0

[nagypeterjob]

https://github.com/bitrise-io/bitrise-step-update-gitops-repository/releases/2.0.0

What to do if the build fails?

At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.

New Pull Request Checklist

Please mark the points which you did / accept.

• [ ] I will not move an already shared step version's tag to another commit
• [x] I read the Step Development Guideline
• [x] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
• [ ] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
• [x] I read and accept the Abandoned Step policy

[bitrise-coresteps-bot]

Don't forget to follow semantic versioning! Breaking changes (including step inputs) should be in major versions only.

step.yml changes compared to previous version:

--- steps/update-gitops-repository/1.1.11/step.yml  2024-09-16 09:18:51
+++ steps/update-gitops-repository/2.0.0/step.yml   2024-09-16 09:18:52
@@ -12,8 +12,8 @@
 source_code_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository
 support_url: https://github.com/bitrise-io/bitrise-step-update-gitops-repository/issues
-published_at: 2024-08-30T14:43:41.665576+02:00
+published_at: 2024-09-16T11:14:58.889457+02:00
 source:
   git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git
-  commit: 88bc497da9869946e6b21b44c7e2bf19ba8ffe05
+  commit: 25035b812e5e340d20ae174ce321baaa76efbab1
 host_os_tags:
 - osx-10.10
@@ -92,4 +92,27 @@
     title: Body of the opened pull request
   pull_request_body: 'Source commit: https://github.com/bitrise-io/bitrise-steplib/commit/8c30f3f34e13b351cd4af3917710e5d732fbf7d7'
+- opts:
+    category: Replacer mode
+    description: "There are situations when simple templating is not sufficient. \nReplacer
+      mode enables matching & replacing values based on a key+delimiter combination,\nacross
+      multiple files.\n"
+    title: Key-value matching mode
+    value_options:
+    - "true"
+    - "false"
+  replacer_mode: false
+- delimiter: =
+  opts:
+    category: Replacer mode
+    description: "Indicates the delimiter between key and value.\nFor example in \"key=value\",
+      \"=\" is the delimiter. \nRequired when \"Replacer mode\" is enabled.\n"
+    title: Delimiter
+- files: null
+  opts:
+    category: Replacer mode
+    description: |
+      List of files to scan for matching key-value pairs.
+      Required when "Replacer mode" is enabled.
+    title: Files
 outputs:
 - PR_URL: null