ci(nightly): explicitly remove previous nightly release

[nikoksr]

Description

Explicitly remove the previous nightly release before creating the new one.

Motivation and Context

I expected the action that creates the nightly release to also remove the old release. It has options for keeping old releases etc but appararently it's none of its business. Thus, we're now explicitly removing the 'nightly' tag before re-creating it.

How Has This Been Tested?

Ran act locally and it successfully removed the old tag and created the new release, all in remote.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (no code change)
• Refactor (refactoring production code)
• Other CI

Checklist:

• My code follows the code style of this project.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• [ x All new and existing tests passed.

[codecov-commenter]

Codecov Report

Base: 55.91% // Head: 55.91% // No change to project coverage 👍

Coverage data is based on head (1f5c955) compared to base (5652317).
Patch has no changes to coverable lines.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #387   +/-   ##
=======================================
  Coverage   55.91%   55.91%           
=======================================
  Files          21       21           
  Lines         719      719           
=======================================
  Hits          402      402           
  Misses        286      286           
  Partials       31       31           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[nikoksr]

@svaloumas this should fix the auto-deploy of the nightly-release. However, I'm still not sure why the action was not fired off at exactly 0:00 am UTC to be honest. Seems to be pretty straight forward to me, when you look at the action file. We'll have to keep an eye on that.