id,page,ref,title,content,breadcrumbs,references
contributing:contributing-release,contributing,contributing-release,Release process,"Datasette releases are performed using tags. When a new release is published on GitHub, a  GitHub Action workflow  will perform the following: 
             
                 
                     Run the unit tests against all supported Python versions. If the tests pass... 
                 
                 
                     Build a Docker image of the release and push a tag to  https://hub.docker.com/r/datasetteproject/datasette 
                 
                 
                     Re-point the ""latest"" tag on Docker Hub to the new image 
                 
                 
                     Build a wheel bundle of the underlying Python source code 
                 
                 
                     Push that new wheel up to PyPI:  https://pypi.org/project/datasette/ 
                 
             
             To deploy new releases you will need to have push access to the main Datasette GitHub repository. 
             Datasette follows  Semantic Versioning : 
             major.minor.patch 
             We increment  major  for backwards-incompatible releases. Datasette is currently pre-1.0 so the major version is always  0 . 
             We increment  minor  for new features. 
             We increment  patch  for bugfix releass. 
             Alpha and beta releases  may have an additional  a0  or  b0  prefix - the integer component will be incremented with each subsequent alpha or beta. 
             To release a new version, first create a commit that updates the version number in  datasette/version.py  and the  the changelog  with highlights of the new version. An example  commit can be seen here : 
             # Update changelog
git commit -m "" Release 0.51a1

Refs #1056, #1039, #998, #1045, #1033, #1036, #1034, #976, #1057, #1058, #1053, #1064, #1066"" -a
git push 
             Referencing the issues that are part of the release in the commit message ensures the name of the release shows up on those issue pages, e.g.  here . 
             You can generate the list of issue references for a specific release by copying and pasting text from the release notes or GitHub changes-since-last-release view into this  Extract issue numbers from pasted text  tool. 
             To create the tag for the release, create  a new release  on GitHub matching the new version number. You can convert the release notes to Markdown by copying and pasting the rendered HTML into this  Paste to Markdown tool . 
             Finally, post a news item about the release on  datasette.io  by editing the  news.yaml  file in that site's repository.","[""Contributing""]","[{""href"": ""https://github.com/simonw/datasette/blob/main/.github/workflows/deploy-latest.yml"", ""label"": ""GitHub Action workflow""}, {""href"": ""https://hub.docker.com/r/datasetteproject/datasette"", ""label"": ""https://hub.docker.com/r/datasetteproject/datasette""}, {""href"": ""https://pypi.org/project/datasette/"", ""label"": ""https://pypi.org/project/datasette/""}, {""href"": ""https://semver.org/"", ""label"": ""Semantic Versioning""}, {""href"": ""https://github.com/simonw/datasette/commit/0e1e89c6ba3d0fbdb0823272952cf356f3016def"", ""label"": ""commit can be seen here""}, {""href"": ""https://github.com/simonw/datasette/issues/581#ref-commit-d56f402"", ""label"": ""here""}, {""href"": ""https://observablehq.com/@simonw/extract-issue-numbers-from-pasted-text"", ""label"": ""Extract issue numbers from pasted text""}, {""href"": ""https://github.com/simonw/datasette/releases/new"", ""label"": ""a new release""}, {""href"": ""https://euangoddard.github.io/clipboard2markdown/"", ""label"": ""Paste to Markdown tool""}, {""href"": ""https://datasette.io/"", ""label"": ""datasette.io""}, {""href"": ""https://github.com/simonw/datasette.io/blob/main/news.yaml"", ""label"": ""news.yaml""}]"