Release v5.0.1

[mariia-aloshyna]

Update master branch after release

[github-actions]

Jest Unit Test Statistics

64 tests  ±0   64 ✔️ ±0   1m 4s ⏱️ -3s
16 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit a1f22a6. ± Comparison against base commit b672dbf.

♻️ This comment has been updated with latest results.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[zburke]

The ticket description is "Release 5.0.1" but the code change bumps the version to 5.1.0. Is this really a release PR, or are you just pulling the release-changelog down onto master from the release branch?

If so, that's fine, but why would we bother publishing a patch-release with nothing except new tests? That seems odd.

[mariia-aloshyna]

The ticket description is "Release 5.0.1" but the code change bumps the version to 5.1.0. Is this really a release PR, or are you just pulling the release-changelog down onto master from the release branch?

If so, that's fine, but why would we bother publishing a patch-release with nothing except new tests? That seems odd.

hey Zak, this is about updating the master changelog after release, I put the Sunflower version to package.json.
Regarding tests - there are only 2 unit tests left and we planned to finish them in Sunflower but we managed to get it done already and the feature is completed, so PO suggested releasing it to Ramsons and closing the feature.