From b690f44fe4ad02c349f98ee0df1e6ab27cc9dcb1 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Thu, 25 May 2023 22:17:46 +0100 Subject: [PATCH] daily-email: add 2023-05-20 --- src/content/daily-email/2023-05-20.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 src/content/daily-email/2023-05-20.md diff --git a/src/content/daily-email/2023-05-20.md b/src/content/daily-email/2023-05-20.md new file mode 100644 index 00000000..af772222 --- /dev/null +++ b/src/content/daily-email/2023-05-20.md @@ -0,0 +1,19 @@ +--- +title: > + A minor breaking change +pubDate: 2023-05-20 +permalink: > + archive/2023/05/20/a-minor-breaking-change +tags: + - software-development +--- + +Today, in the repository of an open-source project, I saw an issue comment saying, "This is a minor breaking change.". + +It detailed what was removed and suggested an alternative. + +I don't know how you define a "minor" breaking change. + +Is it because it's a single line and easy to replace, or is it part of the code that is rarely used by consumers and less likely to cause an issue? + +Regardless, if it's a breaking change, anyone using that project will need to update their code if they use something that was removed, whether it's minor or not.