Skip to content

fix: use caret constraint for ensemble_test_runner's ensemble dependency #2345

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
TheNoumanDev wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −2
Open

fix: use caret constraint for ensemble_test_runner's ensemble dependency #2345

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion tools/ensemble_test_runner/example/pubspec.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ environment:
dependencies:
ensemble:
hosted: https://pub.dev
version: ">=1.2.50 <2.0.0"
version: "^1.2.50"
ensemble_test_runner:
path: ..
flutter:
Expand Down
2 changes: 1 addition & 1 deletion tools/ensemble_test_runner/pubspec.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ environment:
flutter: ">=3.24.0"

dependencies:
ensemble: ">=1.2.50 <2.0.0"
ensemble: "^1.2.50"

@sharjeelyunus sharjeelyunus Aug 21, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not right, we don't wanna leave the ensemble versions open ended, this can cause issues

see, how we are handling the real issue in release-melos-version.yml

we are using --scope and --manual-version from melos here

I think the better way would be to have a an input `Beta: true/false" in release-melos-version.yml instead of managing 2 different pipelines

device_frame: ^1.3.0
ensemble_device_preview: ^1.1.3
flutter:
Expand Down
Loading