Added TwinCAT Dynamic Collections #4
Conversation
|
Merged it, but looks like GitHub changed something in the API used for getting the last release. Will look into it latest in Monday and keep you posted |
|
It might be because I marked it as a Pre-release. Whenever you're ready I could try marking it as a Release. |
|
Ah, might be, anyway I want to debug this issue, we want to make using the Twinpack registry as simple to us as possible |
|
@fisothemes looked into it and the error is actually popping up because all the releases of your repo are pre-releases. I changed the error message a bit, so it is clear what is going on (see https://github.com/Zeugwerk/Twinpack/actions/runs/10126231685/job/28002851708#step:2:57). We don't have support yet for pre-releases, but I added an issue Zeugwerk/Twinpack#133 to support pre-releases. Not sure, when we'll get to this. The goal of the next release of Twinpack is to improve the commandline interface. However, anytime you'll publish a release as 'official' (without the 'pre-release' checkbox), twinpack-registry will pick it up and it will be available in Twinpack. You can also do it for any of the already published (pre-)releases, just edit the release and untick the 'pre-release checkbox'. The GitHub workflow for checking for releases runs automatically once a day (see https://github.com/Zeugwerk/Twinpack/actions) |
|
I originally marked it as pre-release because I had few more data structures to add. I've been using the library heavily for a while now and it's stable enough to be marked as release, I've done that for the last pre-release. Thanks again for spending some time to look into this, no need to rush, I'm not fussed, it's a small change on my part. |
Added TwinCAT Dynamic Collections library.