Upgrade: rubygem-deep_merge version to 1.2.2#11354
Upgrade: rubygem-deep_merge version to 1.2.2#11354SumitJenaHCL wants to merge 4 commits intomicrosoft:3.0-devfrom
Conversation
|
This PR is raised to successfully merge #11360 |
kgodara912
left a comment
There was a problem hiding this comment.
Good for next stage: buddy build pipeline.
1d4dbb4 to
471733e
Compare
|
@SumitJenaHCL Buddy Build shows license issues. https://dev.azure.com/mariner-org/mariner/_build/results?buildId=903947&view=logs&j=bac295d9-f2e0-5165-e63e-e76f383e1a27&t=2e9390e1-fa16-5310-443b-65696d0c38df Can you check them? |
|
Latest buddy build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=916914&view=results |
|
@SumitJenaHCL It looks like license issues are not resolved yet. Can you address them? ##[warning]License issues found. |
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-staticsubpackages, etc.) have had theirReleasetag incremented../cgmanifest.json,./toolkit/scripts/toolchain/cgmanifest.json,.github/workflows/cgmanifest.json)./LICENSES-AND-NOTICES/SPECS/data/licenses.json,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)*.signatures.jsonfilessudo make go-tidy-allandsudo make go-test-coveragepassSummary
What does the PR accomplish, why was it needed?
This PR is to upgrade the package rubygem-deep_merge to version 1.2.2
Change Log
Does this affect the toolchain?
NO
Associated issues
Links to CVEs
Test Methodology