Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tight version coupling #156

Open
friederbluemle opened this issue Feb 16, 2020 · 1 comment
Open

Tight version coupling #156

friederbluemle opened this issue Feb 16, 2020 · 1 comment

Comments

@friederbluemle
Copy link
Member

No clear action items, but we need to re-think/re-evaluate the tight version coupling (especially on patch level) across repositories.

electrode-io/electrode-native#1488
electrode-io/electrode-native#1485
This was referenced Feb 16, 2020
Closed
Merged
@ryanliljestrom
Copy link

Does this include things like versions in the manifest? We have a partial manifest with several privately published MiniApps and react-native packages, and run into a situation where any patch bump in the native dependencies requires an ern upgrade-miniapp on all MiniApp repositories, re-deploy of all MiniApps, and then re-building the cauldron app descriptor before we can generate a new container with the updated code. Could we specify weaker versions in either the manifest for MiniApps, or is there some other way to solve this problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@friederbluemle @ryanliljestrom