-
Notifications
You must be signed in to change notification settings - Fork 811
Updating packages
Geoff Shannon edited this page May 15, 2018
·
19 revisions
- Remember to make the changes against your up-to-date fork to avoid merge conflicts
- Create a topic branch for your library rather than using the master branch
-
Edit the files
- In minimum, update the
+lib-version+
onbuild.boot
- In minimum, update the
- Check library changelog or such for clues if the API has been changed
- Update externs (if the API has changed)
- If the externs are generated, it is probably a good idea to always generate them between major and minor versions (major.minor.patch).
- If the generated extern doesn't contain notes how it was generated, this is a good time add documentation
- Update externs (if the API has changed)
-
Run package script locally and test the package
- If package uses latest Boot-cljsjs, also remember to commit
boot-cljsjs-checksum.edn
file
- If package uses latest Boot-cljsjs, also remember to commit
- Commit with a message adhering to these guidelines
- Create a pull request from your fork