Skip to content

Update QuartoNotebookRunner to 0.17.3 #12870

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.

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MichaelHatherly
Copy link
Contributor

Includes two bug fixes, added a changelog entry about them. These would be safe to backport to the 1.7 release.

@posit-snyk-bot
Copy link
Collaborator

posit-snyk-bot commented Jun 2, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

@cderv
Copy link
Collaborator

cderv commented Jun 2, 2025

Thanks @MichaelHatherly !

These would be safe to backport to the 1.7 release.

@cscheid, this is an interesting question. How do we consider update to QuartoNotebookRunner?

In contrast to knitr or Jupyter, engine: julia is "tied" to a version of QuartoNotebookRunner, in the sense we ship the version information automatically installed within Quarto CLI.

Do we consider it safe to "backport" an update of QuartoNotebookRunner ?

@MichaelHatherly, for more context, our current policy with backport is that only regression (bugs introduced in 1.7 that were not in 1.6). For other bug fixes, we do not backport them.

I see QuartoNotebookRunner 0.17.3 is a bug fix only - are they related to regressions?

When would you switch to 0.18? Could we consider it safe to backport any minor version once we decide 0.17 is the version shipped with Quarto?

Just curious to have this discussion. Thanks

@MichaelHatherly
Copy link
Contributor Author

are they related to regressions?

They are not fixes for regressions in the strict sense of the word I think, though they are non-breaking bug foxes for the juliaup support that has been in since 0.12.0 that broke in certain situations on Windows systems.

When would you switch to 0.18?

When something gets added that is a definite feature addition, such as supporting a new field and the YAML front matter for example. (We should probably consider a v1 soon since it's all been pretty stable recently and I don't foresee and major changes to it going forward.)

@cderv cderv requested a review from cscheid June 2, 2025 16:11
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.

3 participants