Skip to content

Commit

Permalink
Remove travis task to update version number in master in preperation …
Browse files Browse the repository at this point in the history
…for stricter rules (#322)
  • Loading branch information
bameyrick authored Apr 25, 2019
1 parent 4a744eb commit fcf503a
Show file tree
Hide file tree
Showing 3 changed files with 2 additions and 50 deletions.
4 changes: 0 additions & 4 deletions .travis.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,6 @@ jobs:
secure: wOxnxRRtCSxAS88DpUGBjx4ktYo4UQVIAiAozo/AfbyaENuboQJ1THB1CZDRSHzERt7A62/2IB3mRjFj/PyghtYH1CiLojzE5qHSorGimjIzR2eBW2KSWUfBHe8beE5flo3yzh7HQ39yGO4cjY0jvr2dIaYHyU6QkdYPWpG1EN/TkPr4ZEaXAS8zWAzoi3+b4Ya+iHcr1wArblbykYzVuh2tmnJRNHWUdJmZg30965hb/jg8VdpeHQHRHttYdATfq/f09z6BLBOrwcyidE2o8R7s0QOVagnsisTb+EnsUTduueokRQZY1Een70+F0DJPubQ84/eVTxdBmA0vEess1NboBhHKG9Kd3Xbzg3+OlvE84XRrDBvI6AXwgSj40VsYmtNFTJqJCz/ad1LMW5BK6PNTVCIf9CbthZuYwRX9hNwWjoiauGzyh9Z8sfIxXU3pgdIDNtfk+hEjp2p4BqDwcrZ9myjKKDw90y8pxd9ZELEY5nxiIAbfLT1wNVoByNiqHykLOxQurYT7Zj1KefC4UPqRvcIv8VuaGDHpEqz0UW7EfOC7n0QH7vCLMxztXcyrOpxrDCvBGwk2sgK6+vImkPyb1iC29EuOTux1URtot4BK0YgyDl71PpjEVJIYgBXHCh2tW/LGtC7cuw7vMh+PhnIAP8U0Pw65LYteh+WrlDM=
on:
tags: true
- provider: script
script: bash .travis/pu.sh
on:
tags: true
stages:
- name: test
if: tag IS NOT present
Expand Down
39 changes: 0 additions & 39 deletions .travis/pu.sh

This file was deleted.

9 changes: 2 additions & 7 deletions docs/automatic-npm-releasing.md
Original file line number Diff line number Diff line change
@@ -1,16 +1,11 @@
# Automatic npm releasing

When you create a release (and a tag is created) a Travis build will kick off and start building a npm bundle which will be deployed to npm. The task will also update the version value in the `package.json` on master automatically.
When you create a release (and a tag is created) a Travis build will kick off and start building a npm bundle which will be deployed to npm.

Currently the deploy to npm and git commits are deployed/pushed using API keys for Ben Meyrick's (`[email protected]`) GitHub account. If these need changing there are some prerequisites:
Currently the deployment to npm is done using API keys for Ben Meyrick's (`[email protected]`) npm account. If these need changing there are some prerequisites:

### npm account

- You must be a collaborator on the @ons/design-system package
- You may have 2FA enabled but only for authentication
- The API token **must** be encrypted using the Travis CLI

### GitHub account

- You must be an administrator of the repository
- The branch protection rules for `master` should be set to **not** apply to administrators, or Travis won't be able to update the package.json version with the latest tag

0 comments on commit fcf503a

Please sign in to comment.