Skip to content

[Sync to prerelease] Update release-notes.R to bump version fields at release time#1949

Merged
cderv merged 1 commit intoprereleasefrom
sync-1944-to-prerelease
Mar 6, 2026
Merged

[Sync to prerelease] Update release-notes.R to bump version fields at release time#1949
cderv merged 1 commit intoprereleasefrom
sync-1944-to-prerelease

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 6, 2026

Description

Sync of #1944 to prerelease.

Original PR

Update release-notes.R to bump version fields at release time

Extends tools/release-notes.R to automatically update version in both _quarto.yml and _quarto-prerelease-docs.yml during the release process.

Context

PR #1939 added a version field to these files for the prerelease-docs-url shortcode, which compares the version argument to _quarto.yml version to decide whether blog links go to quarto.org or prerelease.quarto.org. For this to work on main, _quarto.yml version must be bumped at release time.

Since release-notes.R runs on the prerelease branch, the version bump propagates to main when prerelease is merged.

What this does

At the end of the script, after updating the download listings:

  • _quarto.yml version → released version (e.g. '1.9')
  • _quarto-prerelease-docs.yml version → next prerelease (e.g. '1.10')

This replaces what was previously a manual step in the release checklist. A companion PR to quarto-cli updates the release checklist accordingly.

Extends the release notes script to also update `version` in
`_quarto.yml` (to the released version) and `_quarto-prerelease-docs.yml`
(to the next prerelease). This automates the version bump that was
previously a manual step, ensuring the `prerelease-docs-url` shortcode
resolves blog post links correctly after merge to main.

(cherry picked from commit 4a9e378)
@cderv
Copy link
Collaborator

cderv commented Mar 6, 2026

/deploy-preview

@cderv cderv merged commit 7858f80 into prerelease Mar 6, 2026
@cderv cderv deleted the sync-1944-to-prerelease branch March 6, 2026 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant