# Publishing For every push to the development, release or master branch some automated steps are done by Travis: setup a version number and publish to npm. The version number is created as folows: * take the version number from the package.json file * use tags: alpha for the development branch, beta for releaase, and latest for master. * ask npm what the most recently published version is for that tag and the current version * add one to the minor version and publish using the tag and new versionnumber Eg. the current version number in package.json is 0.30.0. On a push to development travis starts.\ It finds that the latest release tagged alpha is 0.30.0-alpha.1. It increase the last numer and publishes to 0.30.0-alpha.2\ The components are now available and can be used for example through jsdelivr: This means that you do not need to update the number in package.json for every commit. Details can be found in [.travis.yml](https://github.com/Amsterdam/openstad-components/blob/master/.travis.yml) and [set-publish-version.js](https://github.com/Amsterdam/openstad-components/blob/master/scripts/set-publish-version.js) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.openstad.org/openstad/technical/components/publishing.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.