configcat-feature-flag-sync 0.0.9

[kp-cat]

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.

• [x] 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)
• [x] 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

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

:white_check_mark: kp-cat
:x: Peter Adam Korodi

---

Peter Adam Korodi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[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/configcat-feature-flag-sync/0.0.8/step.yml    2024-09-05 09:56:44
+++ steps/configcat-feature-flag-sync/0.0.9/step.yml    2024-09-05 09:56:45
@@ -19,8 +19,8 @@
 source_code_url: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync/
 support_url: https://configcat.com/support/
-published_at: 2024-04-11T15:23:29.986976+02:00
+published_at: 2024-09-05T11:50:30.594669+02:00
 source:
   git: https://github.com/configcat/bitrise-step-configcat-feature-flag-sync.git
-  commit: 6e5a96302954bcedf5a81974d70edd6b38c524bb
+  commit: a27868235c227bcda815ee0e1430c7fdd6c66b18
 host_os_tags:
 - osx-10.10
@@ -58,10 +58,27 @@
     title: 'Code snippet line count before and after the reference line (min: 1, max:
       10)'
+- exclude_keys: ""
+  opts:
+    summary: e.g. 'featureFlagToExclude1 featureFlagToExclude2'.
+    title: List of feature flag keys that must be excluded from the scan report
+- alias_patterns: ""
+  opts:
+    summary: The regex pattern must include the CC_KEY placeholder that represents
+      the actual feature flag or setting key in your code e.g. '(\w+) = :CC_KEY,const
+      (\w+) = feature_flags\.enabled\(:CC_KEY\)'.
+    title: Comma delimited list of custom regex patterns used to search for additional
+      aliases
 - opts:
-    summary: e.g. 'subfolder/to/scan'
+    summary: The regex pattern must include the CC_KEY placeholder that represents
+      the actual feature flag or setting key in your code e.g. 'feature_flags\.enabled\(:CC_KEY\)'.
+    title: Comma delimited list of custom regex patterns that describe additional
+      feature flag key usages
+  usage_patterns: ""
+- opts:
+    summary: e.g. 'subfolder/to/scan'.
     title: Sub-folder to scan, relative to the repository root folder
   sub_folder: null
 - opts:
-    summary: Turns on or off detailed logging
+    summary: Turns on or off detailed logging.
     title: Detailed logging
     value_options: