Skip to content

Instantly share code, notes, and snippets.

@gr2m

gr2m/semantic-release-and-greenkeeper-demo-outline.md

Last active April 18, 2016 20:10
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save gr2m/a916b0a7e46c0c565da09863b9f701f7 to your computer and use it in GitHub Desktop.
Save gr2m/a916b0a7e46c0c565da09863b9f701f7 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
semantic-release-and-greenkeeper-demo-outline.md

I will give a talk on semantic-release and Greenkeeper this Thursday at Node.js Boston. I want to live-demo publishing packages, update workflows and an accidental breaking change and how Greenkeeper helps with that. I’m looking for a good "story" for what these packages do, how to call them, etc. Any idea? Please ping me on Twitter

Outline

Goal: create a CLI tool / app with a dependency and a sub dependency.

  • Show quickly who to publish all 3 tools with semantic-release
  • Add feature to sub-dependency, feature it shows up in CLI tool (after running npm install) although dependency was not updated.
  • Show tag & changelogs on GitHub
  • enable Greenkeeper on all repos
  • Create fix in sub dependency, show how Greenkeeper does not send a pull request, but still triggers CI build
  • Create fix in sub dependency with unwanted breaking change.
  • Install CLI tool from scratch, show that it breaks now although nothing was changed.
  • Show how Greenkeeper starts pull request because of breaking tests. Change ^1.0.0 to 1.1.0 to contain the accidental change and change commit message to “fix(package): …”
  • Install CLI tool from scratch, show that it no longer breaks.
  • Fix the accidental breaking change in sub dependency
  • GK starts a new pull request because 1.1.1 is out of range for 1.1.0, tests pass, change 1.1.0 to ^1.1.1, change commit message to “fix(package): …”
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment