Skip to content
Juho Teperi edited this page Dec 25, 2017 · 19 revisions
  1. Remember to make the changes against your up-to-date fork to avoid merge conflicts
  2. Create a topic branch for your library rather than using the master branch
  3. Edit the files
    • In minimum, update the +lib-version+ on build.boot
  4. Check library changelog or such for clues if the API has been changed 5. 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
  5. Run package script locally and test the package
    • If package uses latest Boot-cljsjs, also remember to commit boot-cljsjs-checksum.edn file
  6. Commit with a message adhering to these [guidelines]
  7. Create a pull request from your fork

Clone this wiki locally