fix: Use a script to manually control the execution failure of multiple versions
Is there an existing issue for this?
- [x] I have searched the existing issues.
Version
7.0.0-dev.5
Description
melos:
version:
fetchTags: false
updateGitTagRefs: false
message: |
chore(release): publish packages
{new_package_versions}
scripts:
version: melos version -V semi_component:major -V semi_extension:major -V semi_kit:major -V semi_service:major -V semi_theme:major -V semi_util:major --no-changelog --no-git-tag-version
output
PS C:\Users\admin\Desktop\flutter_design> melos run version
melos run version
â””> melos version -V semi_component:major -V semi_extension:major -V semi_kit:major -V semi_service:major -V semi_theme:major -V semi_util:major --no-changelog --no-git-tag-version
â””> RUNNING
melos version
â””> C:\Users\admin\Desktop\flutter_design
The following 6 packages will be updated:
Package Name Current Version Updated Version Update Reason
semi_component 0.0.1 0.1.0 manual versioning
semi_extension 0.0.1 0.1.0 manual versioning
semi_kit 0.0.1 0.1.0 manual versioning
semi_service 0.0.1 0.1.0 manual versioning
semi_theme 0.0.1 0.1.0 manual versioning
semi_util 0.0.1 0.1.0 manual versioning
ERROR: Operation was canceled.
Steps to reproduce
Expected behavior
Screenshots
No response
Additional context and comments
No response
Other
- [ ] I'm interested in working on a PR for this.
Can you elaborate on what is wrong? I don't see any difference in the pictures.
Can you elaborate on what is wrong? I don't see any difference in the pictures.
This is the script I set up, the function I want is to change the version number of the all package every time, but now it will directly indicate that it is canceled
scripts:
version: melos version -V semi_component:major -V semi_extension:major -V semi_kit:major -V semi_service:major -V semi_theme:major -V semi_util:major --no-changelog --no-git-tag-version
Is it possible to fix this issue, it is not possible to manually upgrade the version of multiple dependencies via script, it will automatically cancel the operation
Since you're not in a interactive shell you have to add --yes to your command.
Hello 👋, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.