Canary builds not being published?

[robertroessler]

Artifacts from Github "workflows" -driven builds don't seem to be showing up on the "Canary Builds" page? These stopped appearing right after the last "release" (3.2.25136.1352), but [obviously] repo check-ins are still happening and the triggered builds are still happening (according to the "build history" link)... we just don't see the artifacts any longer.
Are these now showing up elsewhere or the visibility is being suppressed for some reason?

[jxy-s]

GitHub workflow builds aren't published. They're just tests and sanity checks that as we develop against master things aren't breaking. We build so frequently in that workflow, it doesn't make sense to publish every single one of them... and it wouldn't be wise anyway due to code signing.

A build pipeline exists separate from the GitHub workflows which builds and publishes Canary builds. Canary channel builds are published here:
https://github.com/winsiderss/si-builds/releases

Release channel builds, once determined stable, are published to the main repo:
https://github.com/winsiderss/systeminformer/releases

You can also get the latest builds from our website:
https://system-informer.com/downloads

[robertroessler]

First off, thanks for the answer - but the above post has two identical links, and they both are of course actual releases.
I should have been more specific - https://systeminformer.io/canary used to behave as expected, with new "canary" builds appearing quite regularly (presumably triggered by commits), and the https://github.com/winsiderss/systeminformer/actions/workflows/msbuild.yml "workflows" link shows these builds are indeed still happening quite frequently, sort of like how one expects "CI" builds to work.
BUT, none of the output artifacts from these builds are visible on the canary site, and they stopped at the same time as the most recent release.

[jxy-s]

I corrected the link in my original post, thanks.

BUT, none of the output artifacts from these builds are visible on the canary site, and they stopped at the same time as the most recent release.

Those builds have never been published anywhere. They go into the ether never to be seen again, by design.