classicrocker883 / MRiscoCProUI

This is optimized firmware for Voxelab Aquila & Ender3 V2/S1 3D printers.
https://classicrocker883.github.io/
Other
74 stars 17 forks source link

[BUG] Unintended release updates? #68

Closed ThomDietrich closed 10 months ago

ThomDietrich commented 11 months ago

Did you test the latest release build?

Yes, and the problem still exists.

Bug Description

Hey, not a bug with the firmware. Thanks for your work!

I've subscribed to releases in your repository. Good idea in theory but since then I get four release notifications per day. Looks like you regularly replace releases by the daily build!? Is that intended? To me this feels like more like a bug in your CICD toolchain.

Thanks for checking!

Printer Model

Creality Ender-3

Model Type

V2

Your Mainboard

Creality v4.2.7/4.2.2 F103RET6

Other Mainboard Type

No response

Add-ons that could be involved

No response

ProUI?

NoPro

Bed Leveling

UBL - Unified Bed Leveling

Did you include your own configuration files?

Additional information & file uploads

No response

classicrocker883 commented 10 months ago

Ohh shoot I had no idea that was a "thing" that you could do that. and I apologize for the late reply, been super busy.

so for the releases, yes those are Unintended to be the latest release. I should add some kind of marker or note saying "TEST" or something like that. but if the release has no description box with all the info about the release, simply ignore it. also there may not be any assets either to download. Either way, just ignore the notification except maybe the most recent (which is probably the non-test one).

you can also look at the README and at the very top you will see something like Aquila Build Configs :: passing

if it says failing then chances are those releases arent the ones meant to be downloaded.

ThomDietrich commented 10 months ago

All good, thanks. The issues stopped some time after my message. You probably fixed it without knowing. Cheers!

github-actions[bot] commented 8 months ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.