figure out an update and release system for components about victory

[Gastove]

Yesssssssss. I like this a lot -- I'm just not tooling-conversant enough to know how to do it. One idea: a sort of meta-repo (probably this one) that contains all other modules as git submodules. From there, so much scripting.

[colinmegill]

@ryan-roemer Could you chime in here?

[ryan-roemer]

From slack convo, here's where we ended up:

1. fmd-boilerplate add an update-deps script command with npm-update-whatever-that-script-is added as a devDependency and mutate package.json, npm install again, and npm run check. Add docs saying "pull a branch", run update-deps, if it passes, commit the result, push branch and open PR.
2. Automate that in a meta repo or in a not-passed-to-the generator directory in boilerplate -- automation code be programmatic to the GH API or with local checkouts of components... Either way, will be a little wonky, because automagic bulk updates in code rarely work reliably and consistently ;) Often will need manual tweaks

[coopy]

Closed - we have builder ;]