Pubspec file is getting updated with invalid version tag. #843
Labels
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
TL;DR
If a release pull request is made to increment the minor version, and there exist multiple pre-releases following to it, the pubspec file within the release pull request will have an invalid version, as shown in the images below.
Expected behavior
The intended functionality is that if the release pull request is for version
v2.1.0
, the pubspec file should also be updated to versionv2.1.0
without being affected by any +-rc
tags, even if there are multiple pre-release following the release pr.Observed behavior
If a release pull request is created to increase the minor version, and there are multiple subsequent pre-releases, the pubspec file within the release pull request will have a version that combines the new release version with the current+1 pre-release version. For instance, if the release pull request is for version
v2.1.0
and the current pre-release isv2.0.1-rc.2
, the pubspec file version in the release pull request will bev2.1.0+-rc.3
, which is an invalid version.Action YAML
Log output
No response
Additional information
release-please-config.json
The text was updated successfully, but these errors were encountered: