fix: fix release token

[AngryMaciek]

Types of changes 🔧

What type of changes does your code introduce to the project?

• Bugfix (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)
• Other

Checklist ✅

If you're unsure about any of those below, ask explicitly.
This is simply a reminder of what needs to be checked before merging your code.

• I have read the CONTRIBUTING.
• I have performed a self-review of my own code.
• Tests specified with the 'make' framework do not raise any errors.
• I have added tests that prove my fix is effective or that my feature works.
• I have added necessary documentation (if appropriate).
• My changes generate no new warnings.
• I have commented my code, particularly in hard-to-understand areas.

[github-actions]

Dear @AngryMaciek,

It is our utmost pleasure to receive your glorious PR to our humble codebase.
You may kick back & relax for now. Our team will be with you shortly...

---

Fig 1. Typical GitHub repo: PR assignee & a reviewer arguing over typos.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (eb22899) 100.00% compared to head (1604496) 100.00%.

Additional details and impacted files

@@            Coverage Diff            @@
##            master       #64   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines          893       893           
=========================================
  Hits           893       893           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.