Sam Khalaf

@reediculous456 so is this repo not being maintained any longer and users should switch to the fork you created to address Node 12 deprecation ?

Any word on this? are there any plans to patch this action so it does not throw this Node 12 warning and eventually stop working?

@dalanmiller have you tried with `githubocto/[email protected]` ?

@dalanmiller no problem. Actually, that's what I also though, but apparently it was not the case.

Thank you @stefanbuck for confirming it. Now it makes sense at least ;) And again, thanks for this awesome custom action!

@stefanbuck .. it seems that this issue is back again due to a recent code change you committed to v3. Today, I noticed that all checkboxes are broken (checked value...

@stefanbuck , any update on this please?

Hi @stefanbuck and thanks for following up. Yes, I use @v3 tag and it used to work fine with parsing checkboxes the new way (i.e. as arrays), but it stopped...

No it is private. I am positive that v3 stopped working last week and looking at the logs the checkboxes parsing code returned nulls (multiple forms, multiple checkboxes, all same...