So I could have swore I saw official support for beta test versions in HPM a long time go. I could probably dig through the code and figure it out but wondering if anyone already knows how it works or has an example.
I thought there was something where you could add a beta version to the manifest, but I cannot find it in any of the docs.
There is an option in the settings which seems to indicate there is support for it:
Long story short.... I have so much different stuff going on now that it is very hard to make updates and do the thorough testing which I used to do for every version. So I am looking for the best way to release test versions for feedback before I post it in the main package.
1 Like
I think it's:
"betaVersion": "xx.xx.xx"
"betaLocation": "http......"
3 Likes
Thanks I knew I saw it somewhere before, that was probably it. I was only looking at the actual docs and could not find it.
1 Like
that's the sample that Dom invented. When I adopted HPM, and added Bundle support, I wedged in an example in that sample code... not remembering it had Beta examples. Til today. I knew I'd seen it somewhere but couldn't put my finger on it.
3 Likes
Got it done finally [BETA] Zooz Advanced Drivers BETA Updates
Its not great, but it works. The release notes is not separated so I put beta info in the existing one. I dont think you can pick which packages you want beta versions for, its sort of all or none.
Ideally you could just point to a totally different manifest for beta but I know due to the way HPM was designed this is not really possible. I came up with a solution though by putting the beta on a new branch, and then updating the main branch manifest to point to those files. When beta is over I can update the manifest on the beta branch (which is not used for anything) and then merge that along with all the changes to main.
2 Likes
