ci: use prerelease logic

[ReenigneArcher]

Description

Use new pre-release logic.

Screenshot

Issues Fixed or Closed

Type of Change

• 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 not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.77%. Comparing base (9cbbe3c) to head (7c0b5ef).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #265   +/-   ##
=======================================
  Coverage   78.77%   78.77%           
=======================================
  Files          24       24           
  Lines        2869     2869           
=======================================
  Hits         2260     2260           
  Misses        609      609           

Flag	Coverage Δ
Python-2.7-Linux	78.77% <ø> (ø)
Python-2.7-Windows	78.77% <ø> (ø)
Python-2.7-macOS	78.77% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.