Compare commits

...

2 Commits

Author SHA1 Message Date
Colin Eberhardt
68d45b4b9a 0.0.6 2015-08-21 11:05:20 +01:00
Colin Eberhardt
99f44302fe Giving up on travis!
OK, Travis you have defeated me! reverting to a more manual release process
2015-08-21 11:04:46 +01:00
3 changed files with 10 additions and 13 deletions

View File

@@ -11,12 +11,4 @@ addons:
apt:
packages:
- gcc
deploy:
provider: npm
email: ceberhardt@scottlogic.com
api_key:
secure: "Dk69FV717n91CRMv0UqzqZG6mrd4dSwd2PJDf1Fe0GOVPrVG9pmSTUmsk7JGli7EB57ovPGRhE/lcDGnlE+hEVw5DjZhGUUmZIFGg+FdcVomoiTRUYjRLwRUKEVxYw1TGCjJHm4rEx4qdkghahjf1YRYnivOn7ADhdH5THr7uQE="
on:
tags: true
branch: master

11
dist/README.md vendored
View File

@@ -1,4 +1,4 @@
Releases can be found on [npm](https://www.npmjs.com/package/dss-layout).
Releases can be found on [npm](https://www.npmjs.com/package/css-layout).
#Release Process
@@ -6,7 +6,12 @@ Releases can be found on [npm](https://www.npmjs.com/package/dss-layout).
# Ensure that the local codebase is up to date
git fetch upstream master && git checkout FETCH_HEAD
# increment the version number and tag the release
npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease]
```
This will take care of getting the latest version of `upstream/master`, updating the package.json, committing, tagging and pushing back to `upstream/master`. Travis will then take care of building the packages and pushing to npm.
# push the the commit and tag back to upstream
git push --tags upstream HEAD:master
# publish this new version to npm
npm publish
```

View File

@@ -1,6 +1,6 @@
{
"name": "css-layout",
"version": "0.0.5",
"version": "0.0.6",
"description": "Reimplementation of CSS layout using pure JavaScript",
"main": "dist/css-layout.js",
"scripts": {