quaint-beach-19549
05/02/2024, 8:07 AMcolossal-address-99162
05/03/2024, 12:15 AMquaint-beach-19549
05/03/2024, 7:16 AMquaint-beach-19549
05/05/2024, 7:03 AMcolossal-address-99162
05/06/2024, 4:07 PMcolossal-address-99162
05/07/2024, 12:31 AMv<major>.<minor>.<patch>
) in the GitHub repository for the SatoriCyber provider in order for the registry publishing pipeline to pick up the provider. Btw, we also auto update the registry packages by checking for new release tags of the provider on a twice daily cadence so anytime you make any updates to the provider and publish a new release tag we will automatically pick it up and update it on the registry site.quaint-beach-19549
05/07/2024, 5:34 AMquaint-beach-19549
05/07/2024, 5:36 AMquaint-beach-19549
05/08/2024, 11:09 AMcolossal-address-99162
05/08/2024, 3:30 PMdist
directory to your v0.0.1 release you created and should work fine for now (honestly might be easier to just add the workflow). Once this is done, the release should contain the binaries for the different platforms/architectures. See this provider as an example.
Let me know if you need any other assistance here.colossal-address-99162
05/08/2024, 5:17 PMSo whenever I want to update some documentation with examples or other stuff all I need is to create a new release ?correct!!