Version release strategy

[theryansmee]

It occurred to me today that there is a disparity between the functions that are listed in our docs, and the functions that are available in the latest available package 2.22.0.

Would it be worth us looking at only updating docs on package release?

[NetanelBasal]

Yes, you need to check if there is a github hook for a release in actions

[theryansmee]

Ok cool, I'll do a little research and see what I come up with 😊

[theryansmee]

@NetanelBasal So I haven't got access to the project settings to try it out, but it looks like you can select Deployment from the "Let me select individual events" section in the new webhooks setting.

[NetanelBasal]

Where?

[theryansmee]

As I say, i've not played with it but it's here:

[theryansmee]

About 1/2 way down is Deployments- Repository was deployed or a deployment was deleted.

[NetanelBasal]

https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#release

[NetanelBasal]

already released today.

[theryansmee]

Es perfecto! 🔥

[theryansmee]

@NetanelBasal - Just seen you did a release earlier and it looks like the docs updated 🔥

[shaharkazaz]

@theryansmee When I tried it seemed like it didn't work, I reverted back to the push

[theryansmee]

@shaharkazaz - oh really? I assumed it had been my change that did it. I must admit, I did wonder how it would know to trigger it. Especially as we don't use GitHub's built in package registry to deploy our packages.

Hmmm im not really sure then..

For now manual might be better because at least the documentation will be inline with actual functionality?

What are your thoughts?