Repository navigation
fix: widen @adobe/aio-lib-ims peer to ^7 || ^8 to drop deprecated uuid@8 (APPBLD-5070) - #82
Merged
AnujVishwakarma-src merged 2 commits intoSep 9, 2026
Conversation
…d@8 (APPBLD-5070) The peerDependency @adobe/aio-lib-ims@^7 forces npm to install an old nested aio-lib-ims@7 even when the consumer uses aio-lib-ims@8 (which depends on this package). That old ims@7 pulls aio-lib-state@3 -> @azure/cosmos@3 -> uuid@8.3.2 (deprecated). aio-lib-ims-jwt does not import @adobe/aio-lib-ims anywhere, so the peer is vestigial; widening it to ^7 || ^8 lets npm satisfy it with the consumer aio-lib-ims@8 (dedupe), removing the ims@7 -> uuid@8 chain tree-wide. Validation: unit tests 5/5 pass, 100% coverage, lint clean. Consumer proof: with this change packed and applied in aio-cli-plugin-runtime, the nested aio-lib-ims@7 disappears (ims@8 deduped) and uuid@8.3.2 is removed from the production dependency tree. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
aroragarvit666-hue
approved these changes
Sep 9, 2026
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
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.
What
Widen the
@adobe/aio-lib-imspeer dependency range:^7→^7 || ^8.Why
uuid@8.3.2(deprecated) surfaces across the@adobe/aio-clidependency tree. The root cause is this package's peer range:aio-lib-ims@8depends onaio-lib-ims-jwt@^5, so npm installs an old nestedaio-lib-ims@7to satisfy the^7peer — even when the consumer is already onaio-lib-ims@8. That old ims@7 pullsaio-lib-state@3 → @azure/cosmos@3.17.3 → uuid@8.3.2.This package does not import
@adobe/aio-lib-imsanywhere insrc/test(verified) — the peer is vestigial. Widening it to^7 || ^8lets npm satisfy the peer with the consumer'saio-lib-ims@8(dedupe), removing theims@7 → uuid@8chain.Validation
aio-cli-plugin-runtime, the nestedaio-lib-ims@7disappears (aio-lib-ims@8deduped everywhere) anduuid@8.3.2is removed from the production dependency tree🤖 Generated with Claude Code