Skip to content

Update release checklist for version-aware shortcode fields #14169

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cderv merged 1 commit into from
Mar 6, 2026
+5 −3
Merged

Update release checklist for version-aware shortcode fields #14169

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions dev-docs/checklist-make-a-new-quarto-release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,17 +32,19 @@
- [ ] change `docs/prerelease/_highlights.qmd` so its include points to the new version-specific `_highlights.qmd` file (here, 1.5)
- [ ] change `docs/prerelease/_highlights-release.qmd` so its include points to the new version-specific `_highlights.qmd` file (here, 1.4)
- [ ] add the stable version to the older downloads list by editing /docs/download/\_download-older.yml
- [ ] run `quarto run tools/release-notes.R` to generate the release notes
- [ ] run `quarto run tools/release-notes.R` to generate the release notes and bump `version` in `_quarto.yml` (to released version) and `_quarto-prerelease-docs.yml` (to next prerelease)
- [ ] push the changes to `prerelease` branch, ensure they build correctly
- [ ] Merge the `prerelease` branch into `main`, push to `main`
- [ ] ensure the build completes successfully
- [ ] verify `_quarto.yml` `version` on `main` reflects the released version (e.g. `'1.4'`) — needed for `prerelease-docs-url` shortcode to resolve blog links to quarto.org
- [ ] Merge `main` into `prerelease`, push to `prerelease`
- [ ] ensure the build completes successfully
- [ ] Create new tag on `main` with stable release version number (here, `v1.4`) to mark when the new main site version went live
- [ ] `git tag -a v1.4 -m "v1.4"`
- [ ] `git push origin v1.4`
- [ ] Update `prerelease` version number (here, `v1.5`)
- [ ] edit `_quarto-prerelease-docs.yml` to point to the new version
- [ ] Verify version numbers were updated by `tools/release-notes.R`
- [ ] `_quarto.yml` `version` should be the released version (e.g. `'1.4'`)
- [ ] `_quarto-prerelease-docs.yml` `version` should be the next prerelease (e.g. `'1.5'`)
- [ ] publish the release blog post that should exist in https://github.com/quarto-dev/quarto-web/tree/main/docs/blog/posts
- [ ] Create a branch off of `main` (to trigger our PR automation to make the corresponding change to `prerelease`).
- [ ] Removing the `draft: true` line in the metadata
Expand Down
Loading