From 9faf12163a26988aefbd35ae0ec29ded5626ae6a Mon Sep 17 00:00:00 2001 From: Ian Butterworth Date: Wed, 18 Dec 2024 22:38:02 +0000 Subject: [PATCH 1/3] fix guidance if branches --- src/AutoMerge/guidelines.jl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/AutoMerge/guidelines.jl b/src/AutoMerge/guidelines.jl index dd6c4ad6..8bd11194 100644 --- a/src/AutoMerge/guidelines.jl +++ b/src/AutoMerge/guidelines.jl @@ -357,12 +357,12 @@ function breaking_explanation_message(has_release_notes) """ if has_release_notes return """ - This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. + This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. $(example_detail) """ else return """ - This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. + This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. $(example_detail) """ end From 915db2b164dc8a806ef42bedb27fd757396a4561 Mon Sep 17 00:00:00 2001 From: Ian Butterworth Date: Wed, 18 Dec 2024 22:38:19 +0000 Subject: [PATCH 2/3] patch bump --- Project.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Project.toml b/Project.toml index 7eece9bc..0520948e 100644 --- a/Project.toml +++ b/Project.toml @@ -1,7 +1,7 @@ name = "RegistryCI" uuid = "0c95cc5f-2f7e-43fe-82dd-79dbcba86b32" authors = ["Dilum Aluthge ", "Fredrik Ekre ", "contributors"] -version = "10.10.2" +version = "10.10.3" [deps] Base64 = "2a0f44e3-6c83-55bd-87e4-b1978d98bd5f" From 96396784369941a36a740009bd581959c0edd92d Mon Sep 17 00:00:00 2001 From: Ian Butterworth Date: Wed, 18 Dec 2024 22:51:20 +0000 Subject: [PATCH 3/3] update reference tests --- ...t_onepointzero_false_version_0.1.0_point_to_slack_false.md | 4 ++-- ...st_onepointzero_false_version_0.1.0_point_to_slack_true.md | 4 ++-- ...t_onepointzero_false_version_1.0.0_point_to_slack_false.md | 4 ++-- ...st_onepointzero_false_version_1.0.0_point_to_slack_true.md | 4 ++-- ...st_onepointzero_true_version_0.1.0_point_to_slack_false.md | 4 ++-- ...est_onepointzero_true_version_0.1.0_point_to_slack_true.md | 4 ++-- ...st_onepointzero_true_version_1.0.0_point_to_slack_false.md | 4 ++-- ...est_onepointzero_true_version_1.0.0_point_to_slack_true.md | 4 ++-- ...t_onepointzero_false_version_0.1.0_point_to_slack_false.md | 4 ++-- ...st_onepointzero_false_version_0.1.0_point_to_slack_true.md | 4 ++-- ...t_onepointzero_false_version_1.0.0_point_to_slack_false.md | 4 ++-- ...st_onepointzero_false_version_1.0.0_point_to_slack_true.md | 4 ++-- ...st_onepointzero_true_version_0.1.0_point_to_slack_false.md | 4 ++-- ...est_onepointzero_true_version_0.1.0_point_to_slack_true.md | 4 ++-- ...st_onepointzero_true_version_1.0.0_point_to_slack_false.md | 4 ++-- ...est_onepointzero_true_version_1.0.0_point_to_slack_true.md | 4 ++-- 16 files changed, 32 insertions(+), 32 deletions(-) diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md index 475164e9..6ee8d5bb 100644 --- a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md @@ -29,7 +29,7 @@ Please make sure that you have read the [package naming guidelines](https://juli -- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -49,7 +49,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md index 913ffe52..683e022f 100644 --- a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md @@ -29,7 +29,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -49,7 +49,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md index 475164e9..6ee8d5bb 100644 --- a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md @@ -29,7 +29,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -49,7 +49,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md index 913ffe52..683e022f 100644 --- a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md @@ -29,7 +29,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -49,7 +49,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md index 189a927e..6b4af5ce 100644 --- a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md @@ -29,7 +29,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -49,7 +49,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md index a22323d9..18050911 100644 --- a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md @@ -29,7 +29,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -49,7 +49,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md index 475164e9..6ee8d5bb 100644 --- a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md @@ -29,7 +29,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -49,7 +49,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md index 913ffe52..683e022f 100644 --- a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md @@ -29,7 +29,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -49,7 +49,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md index 439c09b5..91fb01ec 100644 --- a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md @@ -25,7 +25,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -45,7 +45,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md index 2551ec36..070e6832 100644 --- a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md @@ -25,7 +25,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -45,7 +45,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md index 439c09b5..91fb01ec 100644 --- a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md @@ -25,7 +25,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -45,7 +45,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md index 2551ec36..070e6832 100644 --- a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md @@ -25,7 +25,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -45,7 +45,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md index d86abb09..bb18f894 100644 --- a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md @@ -25,7 +25,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -45,7 +45,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md index 2384a9f7..ef16c367 100644 --- a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md @@ -25,7 +25,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -45,7 +45,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md index 439c09b5..91fb01ec 100644 --- a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md @@ -25,7 +25,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -45,7 +45,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md index 2551ec36..070e6832 100644 --- a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md @@ -25,7 +25,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change. +- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: @@ -45,7 +45,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
-- This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes. +- This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.
Example of adding release notes with breaking notice If you are using the comment bot `@JuliaRegistrator`, you can add release notes to this registration by re-triggering registration while specifying release notes: