chore: update deno.lock and freeze install during build#40038
chore: update deno.lock and freeze install during build#40038
Conversation
|
Looks like this PR is not ready to merge, because of the following issues:
Please fix the issues and try again If you have any trouble, please check the PR guidelines |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ 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:
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 |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #40038 +/- ##
===========================================
- Coverage 70.57% 70.51% -0.06%
===========================================
Files 3270 3270
Lines 116766 116766
Branches 21091 21057 -34
===========================================
- Hits 82409 82341 -68
- Misses 32304 32361 +57
- Partials 2053 2064 +11
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
🔴 Layne — 2 finding(s)Found 2 issue(s): 2 high. |
Proposed changes (including videos or screenshots)
With the new upgrade of Deno, building the monorepo with yarn build (which causes the apps-engine to run deno cache to cache deno-runtime dependencies) with a different version during development would cause changes to the deno.lock file - this is not desireable. So we freeze the lock file, breaking the build if changes to it would occur.
Issue(s)
Steps to test or reproduce
Further comments