|
1 | 1 | <img src="https://github.com/raw/js-data/js-data/master/js-data.png" alt="js-data logo" title="js-data" align="right" width="64" height="64" />
|
2 | 2 |
|
3 |
| -## js-data-sql [](https://www.npmjs.org/package/js-data-sql) [](https://circleci.com/gh/js-data/js-data-sql/tree/master) [](https://www.npmjs.org/package/js-data-sql) [](https://github.com/js-data/js-data-sql/blob/master/LICENSE) |
| 3 | +## js-data-sql [](https://www.npmjs.org/package/js-data-sql) [](https://circleci.com/gh/js-data/js-data-sql/tree/master) [](https://www.npmjs.org/package/js-data-sql) |
4 | 4 |
|
5 | 5 | Postgres/MySQL/MariaDB/SQLite3 adapter for [js-data](http://www.js-data.io/).
|
6 | 6 |
|
7 | 7 | ### API Documentation
|
8 | 8 | [DSSqlAdapter](http://www.js-data.io/docs/dssqladapter)
|
9 | 9 |
|
10 |
| -### Project Status |
11 |
| - |
12 |
| -__Latest Release:__ [](https://github.com/js-data/js-data-sql/releases) |
13 |
| - |
14 |
| -__Status:__ |
15 |
| - |
16 |
| -[](https://gemnasium.com/js-data/js-data-sql) [](https://www.codacy.com/public/jasondobry/js-data-sql/dashboard) |
17 |
| - |
18 |
| -__Supported Platforms:__ |
19 |
| - |
20 |
| -[](https://github.com/js-data/js-data) |
21 |
| - |
22 | 10 | ### Quick Start
|
23 | 11 | `npm install --save js-data js-data-sql`.
|
24 | 12 |
|
@@ -73,15 +61,29 @@ When submitting issues on GitHub, please include as much detail as possible to m
|
73 | 61 | 1. Contribute to the issue/discussion that is the reason you'll be developing in the first place
|
74 | 62 | 1. Fork js-data-sql
|
75 | 63 | 1. `git clone [email protected]:<you>/js-data-sql.git`
|
76 |
| -1. `cd js-data-sql; npm install; bower install;` |
| 64 | +1. `cd js-data-sql; npm install;` |
77 | 65 | 1. Write your code, including relevant documentation and tests
|
78 |
| -1. Run `grunt test` (build and test) |
| 66 | +1. Run `npm test` (build and test) |
79 | 67 | - You need io.js or Node 4.x that includes generator support without a flag
|
80 | 68 | 1. Your code will be linted and checked for formatting, the tests will be run
|
81 | 69 | 1. The `dist/` folder & files will be generated, do NOT commit `dist/*`! They will be committed when a release is cut.
|
82 | 70 | 1. Submit your PR and we'll review!
|
83 | 71 | 1. Thanks!
|
84 | 72 |
|
| 73 | +#### Have write access? |
| 74 | + |
| 75 | +Here's how to make a release on the `master` branch: |
| 76 | + |
| 77 | +1. Bump `package.json` to the appropriate version. |
| 78 | +1. `npm test` must succeed. |
| 79 | +1. This time, the built `dist/js-data-sql.js` file _will_ be committed, so stage its changes. |
| 80 | +1. Mention the release version in the commit message, e.g. `Stable Version 1.2.3` |
| 81 | +1. Push to master. |
| 82 | +1. Create a git tag. Name it the version of the release, e.g. `1.2.3` |
| 83 | + - Easiest way is to just create a GitHub Release, which will create the tag for you. Name the Release and the git tag the same thing. |
| 84 | +1. `git fetch origin` if you tagged it via GitHub Release, so you can get the tag on your local machine. |
| 85 | +1. `npm publish .` (Make sure you got the version bumped correctly!) |
| 86 | + |
85 | 87 | ### License
|
86 | 88 |
|
87 | 89 | The MIT License (MIT)
|
|
0 commit comments