CI doesn't fail if dependency is not present in client, but present in other clients

[trivikr]

Describe the bug
CI doesn't fail if dependency is not present in client, but present in other clients

To Reproduce (observed behavior)
Noticed in #815

• First commit didn't have updates in package.json because of Codegen doesn't add new dependency in the client if package.json is already present #804 (945c311)
• Dependencies were added manually in second commit (a4bc4a2)
• Dependencies were missed in some packages so they were added in third commit (7a497a9)

Behavior:

• CI failed for first commit feat: codegen for auto-fill idempotency token #815 (comment)
• CI passed for second commit even if dependencies were not present for two packages feat: codegen for auto-fill idempotency token #815 (comment)
• CI passed for third commit feat: codegen for auto-fill idempotency token #815 (comment)

Expected behavior
CI should fail if dependencies aren't added, otherwise they will block release as in #798

[trivikr]

Similar lack of dependency issue was caught in release scripts, and needed to be fixed in #839

[github-actions]

Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.