From bef456642f7a720c56849f6305715d433d18d3ca Mon Sep 17 00:00:00 2001 From: Sam Isaacson Date: Sun, 3 Nov 2024 14:22:30 -0500 Subject: [PATCH] Update dev_guide.md --- docs/src/devdocs/dev_guide.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/src/devdocs/dev_guide.md b/docs/src/devdocs/dev_guide.md index 691b5b3e3f..9f4cfa4cba 100644 --- a/docs/src/devdocs/dev_guide.md +++ b/docs/src/devdocs/dev_guide.md @@ -17,9 +17,11 @@ continuing stability of releases. Before making a release one should 4. Release via the [registration issue](https://github.com/SciML/JumpProcesses.jl/issues/73) with the command: - ```julia + + ``` @JuliaRegistrator register branch=release-15.0.0 ``` + modifying as appropriate for the version you are releasing. If there is subsequently a need to increment the version of a dependency, this @@ -30,4 +32,4 @@ dependency being updated is a non-breaking release, and would have automatically been installed by the package resolver had it not been capped, a patch release should be preferred. If the new release branch is branched from master, *it needs to ensure Project.toml caps are all ≥ to those listed in the previous -Catalyst release branch*. \ No newline at end of file +Catalyst release branch*.