You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docs (https://yarnpkg.com/features/release-workflow) have an example, where updating the version of "common" changes this dependency in server and client.
This is nice, but shouldn't it update version of server and client as well?
That's import if there would be some intermediate packages between common and server (or client) in a more complex monorepo: how is it possible to propagate changes of, say, lib-common through several packages into server?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The docs (https://yarnpkg.com/features/release-workflow) have an example, where updating the version of "common" changes this dependency in server and client.
This is nice, but shouldn't it update version of server and client as well?
That's import if there would be some intermediate packages between common and server (or client) in a more complex monorepo: how is it possible to propagate changes of, say, lib-common through several packages into server?
Beta Was this translation helpful? Give feedback.
All reactions