Commits · bb7e3f6045a5e7b23a04886f9206faec95dc85cb · abdullh.alsoleman / Front-End

18 Sep, 2019 1 commit
- Warn when build number and version can't be parsed on iOS (#40611) · 9a68b0df
  Jenn Magder authored 5 years ago
  
  9a68b0df
31 Jul, 2019 1 commit
- Build number (part after +) is documented as optional, use entire app version... · dd1fb3bc
  Jenn Magder authored 5 years ago
```
Build number (part after +) is documented as optional, use entire app version if not present (#37036)
```
  dd1fb3bc
13 Jul, 2019 1 commit
- Move tools tests into a general.shard directory in preparation to changing how... · d919e694
  Ian Hickson authored 5 years ago
```
Move tools tests into a general.shard directory in preparation to changing how we shard tools tests (#36108)
```
  d919e694
22 Mar, 2019 1 commit
- some formatting of map, parameters and spaces (#29760) · bfa1d25b
  Alexandre Ardhuin authored 5 years ago
  
  bfa1d25b
13 Feb, 2019 1 commit

Refactor build-number/build-name logic. (#27743) · 4b4a9400

KyleWong authored 6 years ago

This PR aims at several things:

1. Use pub_semver to check a version in pubspec.yaml meets the requirements specified in https://semver.org/.
2. Don't limit build-number/build-name as a fixed format. Instead, validate it according to the target(ios/android).
3. Make sure that build-number/build-name are always validated no matter it's specified by the `flutter command` or version in pubspec.yaml.

Fixes #27589

4b4a9400