Bumping pubspec.yaml build number triggers pub get
See original GitHub issueI have a build & deploy script that bumps the build number with this line
perl -i -pe 's/^(version:\s+\d+\.\d+\.\d+\+)(\d+)$/$1.($2+1)/e' pubspec.yaml
However, when I do this, Dart-Code fetches packages from pub
right as the script begins the build/compile stage.
- Are there any issues with
pub get
running simultaneously withflutter build
? - Is there any way to suppress auto
pub get
temporarily in a shell script?
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Conflicting ffi version between packages & failed to get ...
I try to get the pubspec.yaml of tflite_flutter (https://pub.dev/packages/tflite_flutter) and it seems to be conflicting with file_picker (https ...
Read more >pubspec_version - Dart API docs
CLI tool to set/bump the version key in pubspec.yaml. Semver-compliant (Almost. It uses pub_semver which is a bit different.) ...
Read more >Automated Releases - Melos
Automated Releases. Melos is able to automate versioning and publishing of your packages. This includes: incrementing of versions based on commit messages.
Read more >v2.7 - Dart Code - Dart & Flutter support for Visual Studio Code
This version contains no functional changes but updates some internal references ... Saving pubspec.yaml in a Flutter project will no longer run pub...
Read more >Howto setup Gitlab CI/CD for developing and publishing a ...
After that we need to run flutter pub get and we will notice the ... When they do, they need to bump the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If it’s just one project, you could disable
runPubGetOnPubspecChanges
for that one project (using “Workspace Settings” that would be saved at./.vscode/settings.json
). Otherwise, I don’t think there’s really a clean way to fix this without starting to parse pubspec (but I’d prefer not to just for this case).Does it ever complete? My guess here is that your shell script is hitting the
flutter build
before the command kicked off by VS Code has spawned Flutter to aquire a lock. I would expect that once yourflutter build
(in the shell script) completes, it would release the lock and then the VS Code process would complete. Does that happen?