Skip to content

Commit

Permalink
chore(release): update docs, version to 3.4.3
Browse files Browse the repository at this point in the history
  • Loading branch information
aronhelser committed Apr 11, 2018
1 parent e5f3329 commit 3fac729
Show file tree
Hide file tree
Showing 7 changed files with 3,482 additions and 66 deletions.
6 changes: 5 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,10 @@
## Change Log

### 3.4.2 (2018/04/09 18:55 +00:00)
### 3.4.3 (2018/04/11 15:12 +00:00)
- [#207](https://github.com/wwayne/react-tooltip/pull/207) Return tooltip to original position when possible (@hassanbot)
- [#301](https://github.com/wwayne/react-tooltip/pull/301) insert css as first to allow easy css styling without important (@roblan)

### 3.4.2 (2018/04/09 18:58 +00:00)
- [#373](https://github.com/wwayne/react-tooltip/pull/373) fix(example): 'made dev' works again, small fixes. (@aronhelser)
- [#337](https://github.com/wwayne/react-tooltip/pull/337) Fix README show tip usage error (@gaohailang)
- [#359](https://github.com/wwayne/react-tooltip/pull/359) License should use H2 as the previous sections do (@konekoya)
Expand Down
5 changes: 3 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -147,8 +147,9 @@ Same for empty children, if you don't want show the tooltip when the children is
## Article
[How I insert sass into react component](https://medium.com/@wwayne_me/how-i-insert-sass-into-my-npm-react-component-b46b9811c226#.gi4hxu44a)

## Authors
see [AUTHORS](https://github.com/wwayne/react-tooltip/blob/master/AUTHORS.txt)
## Contributing

We welcome your contribution! Fork the repo, make some changes, submit a pull-request! Our [contributing](contributing.md) doc has some details.

## License

Expand Down
24 changes: 24 additions & 0 deletions contributing.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# Contributing

This doc needs help! Please submit your PR...

## Pull request testing

Some notes on testing and releasing.
* For a PR, follow Github's command-line instructions for retrieving the branch with the changes.
* `make dev` starts a development server, open `http://localhost:8888` to see the example website.
* Provide feedback on the PR about your results.

## Doing a release

We really want to use semantic-release instead of this:

* `make deploy` updates the files in the `standalone` directory
* update the version number in `package.json`
- Fixes update the patch number, features update the minor number.
- Major version update is reserved for API breaking changes, not just additions.
* `npm run github-changes -- -n 3.X.Y` to update the changelog
* `git add`, `git commit` and `git push` to get the version to master.
* `git tag -a 3.X.Y -m 3.X.Y` `git push --tags`
* `npm publish`
* add a version on the github release page, based on the tag
Loading

0 comments on commit 3fac729

Please sign in to comment.