Closed nagypeterjob closed 2 months ago
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/2.0.1/step.yml 2024-09-18 10:00:56
+++ steps/update-gitops-repository/2.0.3/step.yml 2024-09-18 10:00:57
@@ -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-09-16T15:53:35.016529+02:00
+published_at: 2024-09-18T12:00:14.992151+02:00
source:
git: https://github.com/bitrise-io/bitrise-step-update-gitops-repository.git
- commit: a88c5a56a5ba24588b61769619564ad03fd3e832
+ commit: 222d8d00f9f069fa3c8155070a02478c6037c8fe
host_os_tags:
- osx-10.10
@@ -40,5 +40,4 @@
- deploy_path: ""
opts:
- is_required: true
title: Path to place rendered templates inside the repository
- deploy_token:
https://github.com/bitrise-io/bitrise-step-update-gitops-repository/releases/2.0.3
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.
bitrise run test
(in the step's repository)bitrise run audit-this-step
(in the step's repository - note, if you don't have this workflow in yourbitrise.yml
, you can copy it from the step template.)