You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: dev-docs/checklist-make-a-new-quarto-release.md
+15-8Lines changed: 15 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,7 @@
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
19
19
-[ ] quarto-dev/quarto-web changes
20
+
20
21
- wait for the downloads file to be automatically updated by the GitHub Action on https://github.com/quarto-dev/quarto-web
21
22
-[ ] wait for https://github.com/quarto-dev/quarto-web/actions/workflows/update-downloads.yml to run (it runs every 15 minutes, or you can manually trigger it)
22
23
- This workflow run rendered the website: https://github.com/quarto-dev/quarto-web/actions/runs/12016407762
@@ -29,7 +30,7 @@
29
30
-[ ] create `docs/prerelease/1.5/{_highlights, index, _pre-release-feature}.qmd` files based on the ones from the previous release
30
31
-[ ] change `docs/prerelease/_highlights.qmd` so its include points to the new version-specific `_highlights.qmd` file (here, 1.5)
31
32
-[ ] change `docs/prerelease/_highlights-release.qmd` so its include points to the new version-specific `_highlights.qmd` file (here, 1.4)
32
-
-[ ] add the stable version to the older downloads list by editing /docs/download/_download-older.yml
33
+
-[ ] add the stable version to the older downloads list by editing /docs/download/\_download-older.yml
33
34
-[ ] run `quarto run tools/release-notes.R` to generate the release notes
34
35
-[ ] push the changes to `prerelease` branch, ensure they build correctly
35
36
-[ ] Merge the `prerelease` branch into `main`, push to `main`
@@ -43,16 +44,14 @@
43
44
-[ ] edit `_quarto-prerelease-docs.yml` to point to the new version
44
45
-[ ] publish the release blog post that should exist in https://github.com/quarto-dev/quarto-web/tree/main/docs/blog/posts
45
46
-[ ] Create a branch off of `main` (to trigger our PR automation to make the corresponding change to `prerelease`).
46
-
-[ ] Removing the `draft: true` line in the metadata
47
-
-[ ] Change the date to match the release date.
47
+
-[ ] Removing the `draft: true` line in the metadata
- Check the "Whether to publish or not the package on chocolatey" checkbox
57
56
- Wait for @cderv to receive email confirmation, no action needed
58
57
-[ ] pypi
@@ -71,3 +70,11 @@
71
70
- **Publishing Production**: You may elect to publish to production pypyi by checking the `Production Release` option
72
71
- Published to: <https://pypi.org/project/quarto-cli/>
73
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>
- Take a sip of tea ☕, bask in the glory of automation.
12
+
-[ ] Trigger update for quarto.org website once new stable release is available
13
+
- Go to quarto-dev/quarto-web repo in [Update Downloads](https://github.com/quarto-dev/quarto-web/actions/workflows/update-downloads.yml) workflow
14
+
- Run the workflow with 'Run Workflow' button on `main` branch.
15
+
This will check the new release, and update the files in quarto-web to update the Download page.
16
+
- While this automation is running, update the release on pypi below.
11
17
-[ ] update release on pypi repo
12
18
- Goto the [quarto-cli-pypi repo](https://github.com/quarto-dev/quarto-cli-pypi)
13
19
- Update `version.txt` to be the version you'd like to publish and commit
@@ -24,4 +30,17 @@
24
30
- **Publishing Production**: You may elect to publish to production pypyi by checking the `Production Release` option
25
31
- Published to: <https://pypi.org/project/quarto-cli/>
26
32
- Take a sip of tea ☕, bask in the glory of automation.
33
+
- [ ] push release to chocolatey (Only once quarto.org download page is updated with the new release)
34
+
- Got to <https://github.com/quarto-dev/quarto-release-bundles/actions/workflows/build-and-publish-choco.yaml>
35
+
- In the "Build Choco package & Publish" workflow, click "Run Workflow" and be sure to check the "Whether to publish or not the package on chocolatey" checkbox
36
+
- Wait for @cderv to receive email confirmation, no action needed.
27
37
- [ ] Update the stable changelog by moving entries to the "in previous release". Use "[release checklist]"in the commit message to make it easier to spot if a new release is needed next month.
38
+
39
+
- Others installers
40
+
- conda-forge: An automated PR will be created to update the package version in the feedstock <github.com/conda-forge/quarto-feedstock>
41
+
- 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.
42
+
- Winget: An automated PR will be created by a winget bot in<github.com/microsoft/winget-pkgs/>.
43
+
- This is community maintained, so no action is needed from us.
44
+
- Scoop: This will be updated automatically in the manifests repo. No action is needed from us. Maintained as personal project by @cderv.
45
+
- Homebrew: This is automated through an homebrew bot to update the cask <https://github.com/Homebrew/homebrew-cask>
Copy file name to clipboardExpand all lines: news/changelog-1.8.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,32 @@
1
1
All changes included in 1.8:
2
2
3
+
## Regression fixes
4
+
5
+
- ([#6607](https://github.com/quarto-dev/quarto-cli/issues/6607)): Add missing beamer template update for beamer theme options: `colorthemeoptions`, `fontthemeoptions`, `innerthemeoptions` and `outerthemeoptions`.
6
+
- ([#12625](https://github.com/quarto-dev/quarto-cli/pull/12625)): Fire resize event on window when light/dark toggle is clicked, to tell widgets to resize.
7
+
- ([#12657](https://github.com/quarto-dev/quarto-cli/pull/12657)): Load Giscus in generated script tag, to avoid wrong-theming in Chrome.
8
+
3
9
## Formats
4
10
11
+
### `html`
12
+
13
+
- ([#12259](https://github.com/quarto-dev/quarto-cli/issues/12259)): Fix conflict between `html-math-method: katex` and crossref popups (author: @benkeks).
14
+
5
15
### `revealjs`
6
16
7
17
- ([#12598](https://github.com/quarto-dev/quarto-cli/pull/12598)): Ensure `.fragment` on an image with caption applies to whole figure.
8
18
9
19
### `docx`
10
20
11
-
- ([#8392](https://github.com/quarto-dev/quarto-cli/issues/8392)): Fix `docx` generation issues in tables
21
+
- ([#8392](https://github.com/quarto-dev/quarto-cli/issues/8392)): Fix `docx` generation issues in tables
12
22
13
23
## Projects
14
24
15
25
### `website`
16
26
17
27
- ([#12551](https://github.com/quarto-dev/quarto-cli/pull/12551)): Improve warning issued when `aliases` would overwrite an existing document.
18
28
- ([#12616](https://github.com/quarto-dev/quarto-cli/issues/12616)): find SVG images in image discovery for listings.
29
+
- ([#12693](https://github.com/quarto-dev/quarto-cli/issues/12693)): Prevent resource exhaustion on large websites by serializing `NotebookContext` information to file instead of the environment.
0 commit comments