Please describe what you did before you encounter the issue.
Clone the repo and build the package.
What did you expect?
Please describe what you did expect to happen.
The package should build against with the lasted dependencies.
What happened actually?
Please describe what happened actually.
It reads the pubspec.lock file and keeps using old dependencies and environments.
According to the guideline of pub.dev, the lock file should not be contained and submitted to CVS.
For regular packages, don’t commit the pubspec.lock file. Regenerating the pubspec.lock file lets you test your package against the latest compatible versions of its dependencies.
Is it a security issue?
No.
What did you do?
Clone the repo and build the package.
What did you expect?
The package should build against with the lasted dependencies.
What happened actually?
It reads the
pubspec.lock
file and keeps using old dependencies and environments.According to the guideline of pub.dev, the lock file should not be contained and submitted to CVS.
Ref: https://dart.dev/guides/libraries/private-files
Your environment?
N/A
Sample project
N/A