fix: Update pubspec.lock to resolve stale worker_manager git ref#4447
Conversation
Signed-off-by: dab246 <tdvu@linagora.com>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
No application code in the PR — skipped Code Health checks.
See analysis details in CodeScene
Quality Gate Profile: The Bare Minimum
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.
Issue
Root cause
The locked commit (
dd04544) on branchhotfix/worker-init-memory-leakinlinagora/worker_managerwas no longer resolvable, causingflutter pub getto fail withCould not find a file named pubspec.yaml. This happens when the remote branch is force-pushed or rebased after the lock file was last generated. Regeneratedpubspec.lockto point to the current HEAD of the branch.Side effect
#4435