|
2 | 2 | - [ ] create a branch `v1.x`, where x is the version being released |
3 | 3 | - `git checkout -b v1.4` |
4 | 4 | - `git push origin v1.4` |
5 | | -- [ ] mark the current release as the stable release in the `main` branch |
| 5 | +- [ ] mark the current release as the new release in the `main` branch |
6 | 6 | - [ ] edit QUARTO_VERSION line in `/configuration` to be the new version (e.g. `1.5`) |
7 | 7 | - [ ] push the changes to the `main` branch |
8 | 8 | - [ ] kick off a v1.5 build in GHA: https://github.com/quarto-dev/quarto-cli/actions/workflows/create-release.yml |
9 | 9 | - [ ] ensure the build completes successfully |
10 | 10 | - [ ] mark v1.4 release as stable |
11 | | - - go to https://github.com/quarto-dev/quarto-cli/releases |
12 | | - - find the latest v1.4 release and edit, (eg https://github.com/quarto-dev/quarto-cli/releases/edit/v1.4.549) |
13 | | - - at the bottom of the page, there will be two checkboxes, "Set as pre-release" and "Set as latest release": |
14 | | - - "Set as pre-release" should be unchecked, and |
15 | | - - "Set as latest release" should be checked. |
| 11 | + - [ ] go to https://github.com/quarto-dev/quarto-cli/releases |
| 12 | + - [ ] find the latest v1.4 release and edit, (eg https://github.com/quarto-dev/quarto-cli/releases/edit/v1.4.549) |
| 13 | + - [ ] at the bottom of the page, there will be two checkboxes, "Set as pre-release" and "Set as latest release": |
| 14 | + - [ ] "Set as pre-release" should be unchecked, and |
| 15 | + - [ ] "Set as latest release" should be checked. |
16 | 16 | - [ ] once the v1.5 build completes, edit the quarto.org website configuration on https://github.com/quarto-dev/quarto-web to reflect the new version |
17 | 17 | - this means flipping the profile group configuration in `_quarto.yml` from `[rc,prelease]` to `[prerelease,rc]` |
18 | 18 | - [ ] push the changes to the `main` branch |
|
30 | 30 | - [ ] create `docs/prerelease/1.5/{_highlights, index, _pre-release-feature}.qmd` files based on the ones from the previous release |
31 | 31 | - [ ] change `docs/prerelease/_highlights.qmd` so its include points to the new version-specific `_highlights.qmd` file (here, 1.5) |
32 | 32 | - [ ] change `docs/prerelease/_highlights-release.qmd` so its include points to the new version-specific `_highlights.qmd` file (here, 1.4) |
33 | | - - [ ] add the stable version to the older downloads list, like [this example](https://github.com/quarto-dev/quarto-web/commit/85ef62ec5036026d62d57f9cfb190d8b923b2d43) |
34 | | - - [ ] run `quarto run tools/release-notes.R` to generate the release notes |
| 33 | + - [ ] add the stable version to the older downloads list by editing /docs/download/\_download-older.yml |
| 34 | + - [ ] run `quarto run tools/release-notes.R` to generate the release notes |
35 | 35 | - [ ] push the changes to `prerelease` branch, ensure they build correctly |
36 | | - - [ ] Merge the `prerelease` branch into `main` |
| 36 | + - [ ] Merge the `prerelease` branch into `main`, push to `main` |
37 | 37 | - [ ] ensure the build completes successfully |
38 | | - - [ ] Merge `main` into `prerelease` |
| 38 | + - [ ] Merge `main` into `prerelease`, push to `prerelease` |
39 | 39 | - [ ] ensure the build completes successfully |
40 | | - - [ ] Create new tag on `main` (here, `v1.5`) |
41 | | - - [ ] `git tag -a v1.5 -m "v1.5"` |
42 | | - - [ ] `git push origin v1.5` |
| 40 | + - [ ] Create new tag on `main` with stable release version number (here, `v1.4`) to mark when the new main site version went live |
| 41 | + - [ ] `git tag -a v1.4 -m "v1.4"` |
| 42 | + - [ ] `git push origin v1.4` |
43 | 43 | - [ ] Update `prerelease` version number (here, `v1.5`) |
44 | 44 | - [ ] edit `_quarto-prerelease-docs.yml` to point to the new version |
45 | 45 | - [ ] publish the release blog post that should exist in https://github.com/quarto-dev/quarto-web/tree/main/docs/blog/posts |
46 | | - by removing the `draft: true` line in the metadata and changing the date to match the release date. Do this on a branch off of `main` to trigger our PR automation to make the corresponding change to `prerelease`. |
| 46 | + - [ ] Create a branch off of `main` (to trigger our PR automation to make the corresponding change to `prerelease`). |
| 47 | + - [ ] Removing the `draft: true` line in the metadata |
| 48 | + - [ ] Change the date to match the release date. |
47 | 49 |
|
48 | 50 | - [ ] Update https://github.com/quarto-dev/quarto-cli/blob/main/CITATION.cff |
49 | 51 | - [ ] Packaging and package managers, etc |
50 | | - - TBD winget, etc? |
51 | | - - [ ] chocolatey |
52 | | - - https://github.com/quarto-dev/quarto-release-bundles/ |
53 | | - - Go to "Select 'Publish Quarto PyPi'" |
54 | | - - [ ] Click "Run Workflow" |
| 52 | + - [ ] chocolatey (Only once quarto.org download page is updated with the new release) |
| 53 | + - https://github.com/quarto-dev/quarto-release-bundles/actions/workflows/build-and-publish-choco.yaml |
| 54 | + - [ ] In "Build Choco package & Publish" workflow page, click "Run Workflow" |
55 | 55 | - Check the "Whether to publish or not the package on chocolatey" checkbox |
56 | 56 | - Wait for @cderv to receive email confirmation, no action needed |
57 | 57 | - [ ] pypi |
58 | | - - Goto the [quarto-cli-pypi repo](https://github.com/quarto-dev/quarto-cli-pypi) |
59 | | - - Update `version.txt` to be the version you'd like to publish and commit |
| 58 | + - Go to the [quarto-cli-pypi repo](https://github.com/quarto-dev/quarto-cli-pypi) |
| 59 | + - [ ] Update `version.txt` to be the version you'd like to publish and commit |
60 | 60 | - Go to actions |
61 | 61 | - Select 'Publish Quarto PyPi' |
62 | 62 | - [ ] Click "Run Workflow" |
|
70 | 70 | - **Publishing Production**: You may elect to publish to production pypyi by checking the `Production Release` option |
71 | 71 | - Published to: <https://pypi.org/project/quarto-cli/> |
72 | 72 | - Take a sip of tea ☕, bask in the glory of automation. |
| 73 | + - Others installers |
| 74 | + - conda-forge: An automated PR will be created to update the package version in the feedstock <github.com/conda-forge/quarto-feedstock> |
| 75 | + - This is community maintained, so no action is needed from us - except maybe helping if there are issues with the PR. We are assigned as reviewers to the PR. |
| 76 | + - Winget: An automated PR will be created by a winget bot in <github.com/microsoft/winget-pkgs/>. |
| 77 | + - This is community maintained, so no action is needed from us. |
| 78 | + - Scoop: This will be updated automatically in the manifests repo. No action is needed from us. Maintained as personal project by @cderv. |
| 79 | + - Homebrew: This is automated through an homebrew bot to update the cask <https://github.com/Homebrew/homebrew-cask> |
| 80 | + - Manisfest: <https://github.com/Homebrew/homebrew-cask/blob/master/Casks/q/quarto.rb> |
0 commit comments