[2.x] Check in yarn.lock for 2.x branch#1671
Merged
cwperks merged 2 commits intoopensearch-project:2.xfrom Nov 29, 2023
Merged
Conversation
Signed-off-by: Derek Ho <dxho@amazon.com>
cwperks
approved these changes
Nov 28, 2023
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 2.x #1671 +/- ##
=======================================
Coverage 66.29% 66.29%
=======================================
Files 93 93
Lines 2344 2344
Branches 312 312
=======================================
Hits 1554 1554
Misses 720 720
Partials 70 70 ☔ View full report in Codecov by Sentry. |
derek-ho
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Similar to: #1668
This PR removes yarn.lock from gitignore, and checks in the current version of the generated yarn.lock file, after running yarn install. Yarn.lock provides a few benefits:
Provides reproducibility, by being a source of truth for which versions of each dependency were downloaded. This also allows for debugging - if package.json specifies ^1.2.0, you could be using 1.2.0, 1.2.1, etc.
Includes integrity hash to make sure you are downloading from a trusted source
Category
[Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation]
Why these changes are required?
What is the old behavior before changes and new behavior after changes?
Issues Resolved
[List any issues this PR will resolve (Is this a backport? If so, please add backport PR # and/or commits #)]
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.