Use dependencies.io Lerna support & disable issue creation

[Hypnosphi]

See Hypnosphi#85

[codecov]

Codecov Report

Merging #1803 into release/3.3 will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           release/3.3    #1803   +/-   ##
============================================
  Coverage        22.24%   22.24%           
============================================
  Files              325      325           
  Lines             6522     6522           
  Branches           831      832    +1     
============================================
  Hits              1451     1451           
+ Misses            4448     4425   -23     
- Partials           623      646   +23

Impacted Files	Coverage Δ
app/vue/src/server/utils.js	0% <0%> (-53.58%)	⬇️
app/react/src/client/preview/error_display.js	0% <0%> (ø)	⬆️
addons/storyshots/src/test-bodies.js	19.14% <0%> (ø)	⬆️
addons/info/src/components/types/ArrayOf.js	14.28% <0%> (ø)	⬆️
lib/ui/src/modules/shortcuts/actions/shortcuts.js	22.41% <0%> (ø)	⬆️
addons/knobs/src/components/types/Color.js	8.1% <0%> (ø)	⬆️
lib/ui/src/modules/ui/routes.js	0% <0%> (ø)	⬆️
addons/info/src/components/types/ObjectType.js	14.28% <0%> (ø)	⬆️
...react-native/src/manager/components/PreviewHelp.js	0% <0%> (ø)	⬆️
lib/ui/src/modules/ui/libs/filters.js	47.36% <0%> (ø)	⬆️
... and 28 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a268c50...3a6b832. Read the comment docs.

[ndelangen]

why based on 3.3 ?.
I think we should base this on master.

[Hypnosphi]

master doesn't have yarn.lock

[Hypnosphi]

After a discussion in slack, I disabled issue creators:

hypnos [2:52 AM] 
Do we want issues for major updates in deps? https://github.com/Hypnosphi/storybook/issues
 

norbert 
[2:56 AM] 
what do you mean?


hypnos [3:06 AM] 
The recommended setup for `dependencies.io` is PRs for minors and patches, issues for majors (edited)


shilman 
[3:28 AM] 
sounds a little heavy-handed to me, but that’s just personal preference


[3:28] 
i wouldn’t do issues if it was up to me, but i am also open to being pursuaded (edited)


dduan
[5:47 PM] 
I think it just creates unnecessary spam and nothing actionable. Perhaps a few people want to own upgrading dependencies and be assigned those issues? We have enough open tickets already.

[ndelangen]

I think we want to hold this until #1810

[Hypnosphi]

Ok, I'll add both to 3.3 milestone (see #1803 (comment))

[Hypnosphi]

In fact, the command has to stay the same: the bootstrap script won't work without root depandencies

[ndelangen]

Ok, just to get everything clear:

• Merging this would initially do nothing, since the tool would only trigger on master right?
• This would replace greenkeeper completely, after this lands on master, we should disable greenkeeper.

[Hypnosphi]

Both true

[Hypnosphi]

I don't think I understand what's going on here: https://circleci.com/gh/storybooks/storybook/12142?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

[ndelangen]

I think the best way to proceed with this, is to get yarn-workspaces and yarn lock files on master and get this merged to master.

What do you think @Hypnosphi @shilman @igor-dv @storybooks/team ?

---

Greenkeeper has already been disabled for the entire organisation

[Hypnosphi]

I will do that as long as everyone is OK with it

[danielduan]

seems reasonable to me. This is a developer oriented change so merging to master wouldn't really affect the product itself.

[ndelangen]

@Hypnosphi Can you make the PR? I think it's a go.

[Hypnosphi]

Should it be one PR for yarn and then another one for dependencies.io?

[ndelangen]

Let's do yarn & workspaces first, and then dependencies.io after