Skip to content

Commit 765f39c

Browse files
authored
prepare v0.15 (#282)
1 parent ad55690 commit 765f39c

File tree

2 files changed

+6
-4
lines changed

2 files changed

+6
-4
lines changed

CHANGELOG.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,15 +5,15 @@ All notable changes to this project will be documented in this file.
55
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
66
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
77

8-
## Unreleased
8+
## [v0.15.0] - 2025-03-14
99

1010
### Added
1111

12-
- New socket server command `status` that returns a string describing the current server status, including information for each active worker, as well as `forceclose` which is the forced version of `close` that can shut down a worker even if it's currently running [#229](https://github.com/PumasAI/QuartoNotebookRunner.jl/pull/229).
12+
- New socket server command `status` that returns a string describing the current server status, including information for each active worker, as well as `forceclose` which is the forced version of `close` that can shut down a worker even if it's currently running [#229].
1313

1414
### Changed
1515

16-
- Socket server commands `run`, `close` and `stop` will error if a file lock is currently held (a file worker is running) instead of waiting potentially a long time for that lock to open. Those locks were always intended only as mutation protection and not a queueing mechanism, they only behaved that way by accident and in case some worker hangs, it's impractical that further `quarto render` commands just add on top of the pile without a message [#229](https://github.com/PumasAI/QuartoNotebookRunner.jl/pull/229).
16+
- Socket server commands `run`, `close` and `stop` will error if a file lock is currently held (a file worker is running) instead of waiting potentially a long time for that lock to open. Those locks were always intended only as mutation protection and not a queueing mechanism, they only behaved that way by accident and in case some worker hangs, it's impractical that further `quarto render` commands just add on top of the pile without a message [#229].
1717

1818
## [v0.14.0] - 2025-02-26
1919

@@ -340,6 +340,7 @@ caching is enabled. Delete this folder to clear the cache. [#259]
340340
[v0.13.1]: https://github.com/PumasAI/QuartoNotebookRunner.jl/releases/tag/v0.13.1
341341
[v0.13.2]: https://github.com/PumasAI/QuartoNotebookRunner.jl/releases/tag/v0.13.2
342342
[v0.14.0]: https://github.com/PumasAI/QuartoNotebookRunner.jl/releases/tag/v0.14.0
343+
[v0.15.0]: https://github.com/PumasAI/QuartoNotebookRunner.jl/releases/tag/v0.15.0
343344
[#9]: https://github.com/PumasAI/QuartoNotebookRunner.jl/issues/9
344345
[#11]: https://github.com/PumasAI/QuartoNotebookRunner.jl/issues/11
345346
[#14]: https://github.com/PumasAI/QuartoNotebookRunner.jl/issues/14
@@ -399,6 +400,7 @@ caching is enabled. Delete this folder to clear the cache. [#259]
399400
[#194]: https://github.com/PumasAI/QuartoNotebookRunner.jl/issues/194
400401
[#209]: https://github.com/PumasAI/QuartoNotebookRunner.jl/issues/209
401402
[#211]: https://github.com/PumasAI/QuartoNotebookRunner.jl/issues/211
403+
[#229]: https://github.com/PumasAI/QuartoNotebookRunner.jl/issues/229
402404
[#232]: https://github.com/PumasAI/QuartoNotebookRunner.jl/issues/232
403405
[#238]: https://github.com/PumasAI/QuartoNotebookRunner.jl/issues/238
404406
[#248]: https://github.com/PumasAI/QuartoNotebookRunner.jl/issues/248

Project.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
name = "QuartoNotebookRunner"
22
uuid = "4c0109c6-14e9-4c88-93f0-2b974d3468f4"
33
authors = ["Michael Hatherly <[email protected]>", "Julius Krumbiegel <[email protected]>"]
4-
version = "0.14.0"
4+
version = "0.15.0"
55

66
[deps]
77
BSON = "fbb218c0-5317-5bc6-957e-2ee96dd4b1f0"

0 commit comments

Comments
 (0)