Skip to content

Upgrade: rubygem-deep_merge version to 1.2.2#11354

Open
SumitJenaHCL wants to merge 4 commits intomicrosoft:3.0-devfrom
SumitJenaHCL:topic_rubygem-deep_merge
Open

Upgrade: rubygem-deep_merge version to 1.2.2#11354
SumitJenaHCL wants to merge 4 commits intomicrosoft:3.0-devfrom
SumitJenaHCL:topic_rubygem-deep_merge

Conversation

@SumitJenaHCL
Copy link
Copy Markdown
Contributor

@SumitJenaHCL SumitJenaHCL commented Dec 8, 2024

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

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
  • SPECS-EXTENDED/rubygem-deep_merge/rubygem-deep_merge.signatures.json
  • SPECS-EXTENDED/rubygem-deep_merge/rubygem-deep_merge.spec
  • cgmanifest.json
Does this affect the toolchain?

NO

Associated issues
  • #xxxx
Links to CVEs
Test Methodology
  • Local Build

@SumitJenaHCL SumitJenaHCL requested review from a team as code owners December 8, 2024 21:21
@SumitJenaHCL
Copy link
Copy Markdown
Contributor Author

This PR is raised to successfully merge #11360

@SumitJenaHCL SumitJenaHCL marked this pull request as draft January 2, 2025 10:49
@SumitJenaHCL SumitJenaHCL marked this pull request as ready for review January 2, 2025 12:42
Copy link
Copy Markdown
Contributor

@kgodara912 kgodara912 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good for next stage: buddy build pipeline.

@SumitJenaHCL SumitJenaHCL requested a review from kgodara912 July 23, 2025 04:33
@SumitJenaHCL SumitJenaHCL force-pushed the topic_rubygem-deep_merge branch from 1d4dbb4 to 471733e Compare July 23, 2025 07:22
@microsoft-github-policy-service microsoft-github-policy-service Bot added Packaging specs-extended PR to fix SPECS-EXTENDED 3.0-dev PRs Destined for AzureLinux 3.0 labels Jul 23, 2025
@sandeepkarambelkar
Copy link
Copy Markdown
Contributor

@sandeepkarambelkar
Copy link
Copy Markdown
Contributor

@sandeepkarambelkar
Copy link
Copy Markdown
Contributor

@sandeepkarambelkar
Copy link
Copy Markdown
Contributor

@SumitJenaHCL It looks like license issues are not resolved yet. Can you address them?

##[warning]License issues found.
WARN: (rubygem-deep_merge-doc-1.2.2-1.azl3.noarch.rpm) has license warnings:
bad %doc files:
/usr/lib/ruby/gems/3.3.0/doc/deep_merge-1.2.2/rdoc/LICENSE.html
/usr/lib/ruby/gems/3.3.0/doc/deep_merge-1.2.2/ri/page-LICENSE.ri

@sandeepkarambelkar
Copy link
Copy Markdown
Contributor

@sandeepkarambelkar
Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.0-dev PRs Destined for AzureLinux 3.0 Packaging specs-extended PR to fix SPECS-EXTENDED

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants