-
Notifications
You must be signed in to change notification settings - Fork 367
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add explicit build step in release_process.txt
- Loading branch information
Showing
1 changed file
with
1 addition
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,10 @@ | ||
- Change README if necessary | ||
- Write release notes | ||
- Change version number in package.json | ||
- Build using node builder/build.js | ||
- Commit and push | ||
- Update version number in bower.json in rangy-release | ||
- Update code files in rangy-release | ||
- Update files in lib | ||
- Create release in GitHub. Probably an API to do this. Tag and provide release notes as .md file as script argument | ||
- Update npm with `npm publish` | ||
- Update Bower by adding tag to rangy-release and pushing tags to GitHub |