Updating packages

Jump to bottom Edit New page

Juho Teperi edited this page Dec 25, 2017 · 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+ on build.boot
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 to add those: https://github.com/cljsjs/packages/wiki/Creating-Externs#document-the-extern-creation-process
Run package script locally and test the package
- If package uses latest Boot-cljsjs, also remember to commit boot-cljsjs-checksum.edn file
Commit with a message adhering to these [guidelines]
Create a pull request from your fork