Great job. Please considering new trigger features for GitHub Actions.

Dear Developers,

I am currently using the Trigger Pipeline plugin for OutSystems and have come across a potential inconsistency I'd like to discuss with you. I have observed that the version value displayed on the Trigger Dashboard differs from the one shown in the Service Center for the same application.

To ensure I understand and can track application modifications effectively, I would appreciate your guidance on how I can associate the Trigger Pipeline data with the metadata from the same application or module within the Service Center.

Looking at the main features of the Trigger Pipeline plugin, it's clear it's designed to trigger a CI/CD pipeline in an external server when new versions or tags become available for the OutSystems applications. This functionality, in theory, should align the data of the trigger pipeline and the Service Center. However, it appears there might be a discrepancy, as noted above.

Could you please advise on the possible reasons for this discrepancy and how I might resolve it? Also, I would appreciate your insight into where and how the data viewed by the Trigger Pipeline is stored.

Thank you in advance for your time and support.

This is really a nice component. Maybe a little more documentation on how often the "automatically in background process" checks for new versions and how it is possible (should you wish to) disable the automatic deployment and only do it from ADO when the ADO trigger runs.