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.

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

chore(release): Add release automation #162

Merged
merged 1 commit into from
Aug 6, 2016
Merged

Conversation

joshwiens
Copy link
Contributor

Please check if the PR fulfills these requirements

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Other... Please describe:

What is the current behavior? (You can also link to an open issue here)
Publishing was a completely manual process.

What is the new behavior?
An authorized user can execute a single npm command to push a new tag to the npm registry

Does this PR introduce a breaking change?

  • Yes
  • No

If this PR contains a breaking change, please describe the following...

  • Impact: None - Internal Process
  • Migration path for existing applications: N/A
  • Github Issue(s) this is regarding:

Other information:

  • Add publish script and process documentation.
  • Add npm script to publish to npm.
  • Update build:dist to use cross-env library.
  • Updates npmignore to clean up deployment package.

Final deployment package looks like this ..

screen shot 2016-08-05 at 7 16 52 pm

Add publish script and process documentation.
Add npm script to publish to npm.
Update `build:dist` to use cross-env library.
Updates npmignore to clean up deployment package.
@MikaAK MikaAK merged commit 77ba64c into master Aug 6, 2016
@joshwiens joshwiens deleted the d3viant0ne-ScriptedRelease branch August 6, 2016 02:11
@@ -1,2 +1,13 @@
example/

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of a big .npmignore to maintain just use the files property in your package.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants