Conversation
|
|
flxapps
force-pushed
the
fix/untrack-example-pubspec-lock
branch
from
544642d to
301fffb
Compare
…version constraints
There was a problem hiding this comment.
Pull request overview
Removes the generated lockfile from the tracked sources and updates ignore rules so it doesn’t get re-added, while also adjusting a couple of dependency constraints in the package pubspec.yaml.
Changes:
- Delete
example/pubspec.lockfrom the repository. - Add
example/pubspec.lockto.gitignore. - Pin
mtrust_urp_coreandmtrust_urp_uito exact versions inpubspec.yaml(previously caret-ranged).
Reviewed changes
Copilot reviewed 1 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
pubspec.yaml |
Pins mtrust_urp_core / mtrust_urp_ui dependency versions. |
example/pubspec.lock |
Removes the previously committed generated lockfile. |
.gitignore |
Ignores the example lockfile to keep it untracked going forward. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| mtrust_urp_core: 9.1.0-12 | ||
| mtrust_urp_types: ^6.2.0 | ||
| mtrust_urp_ui: ^9.1.0-12 | ||
| mtrust_urp_ui: 9.1.0-12 |
There was a problem hiding this comment.
The change from caret constraints to exact versions for mtrust_urp_core and mtrust_urp_ui is inconsistent with the rest of the dependency constraints (which mostly use ^...) and seems unrelated to the PR goal of untracking the example lockfile. Unless you intentionally need to pin these packages, consider restoring a compatible range (e.g., caret) to avoid unnecessarily restricting dependency resolution for consumers.
cf. title