You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running pub_release from the alpha.11 build the following error is returned:
This occurs when trying to release pubspec_manager using the current package version number.
Updated pubspec.yaml version to 0.9.0
Regenerating version file at /home/bsutton/git/pubspec_manager/lib/src/version/version.g.dart
Running 'pub get' to ensure package is ready to publish
Found git project.
No pre release hooks found in /home/bsutton/git/pubspec_manager/tool/pre_release_hook
Generating release notes.
Would you like to edit the /home/bsutton/git/pubspec_manager/CHANGELOG.md notes (y/n): y
Unhandled exception:
Bad state: stdio is not connected
#0 _ProcessImpl.stdout (dart:io-patch/process_patch.dart:530:19) #1 _startIsolate. (package:dcli/src/process/process/process_in_isolate.dart:89:26)
The text was updated successfully, but these errors were encountered:
I do actually have a partial fix on master for this issue and with a little more work it is completely fixable.
However at the moment I'm trying to deal with a bigger issue:
When running pub_release from the alpha.11 build the following error is returned:
This occurs when trying to release pubspec_manager using the current package version number.
Updated pubspec.yaml version to 0.9.0
Regenerating version file at /home/bsutton/git/pubspec_manager/lib/src/version/version.g.dart
Running 'pub get' to ensure package is ready to publish
Found git project.
No pre release hooks found in /home/bsutton/git/pubspec_manager/tool/pre_release_hook
Generating release notes.
Would you like to edit the /home/bsutton/git/pubspec_manager/CHANGELOG.md notes (y/n): y
Unhandled exception:
Bad state: stdio is not connected
#0 _ProcessImpl.stdout (dart:io-patch/process_patch.dart:530:19)
#1 _startIsolate. (package:dcli/src/process/process/process_in_isolate.dart:89:26)
The text was updated successfully, but these errors were encountered: