# Notify of major changes to collection

**URL:** <https://discourse.nodered.org/t/notify-of-major-changes-to-collection/82455>\
**Category:** Developing Nodes\
**Created:** [30 October 2023 02:22 UTC](https://discourse.nodered.org/t/notify-of-major-changes-to-collection/82455 "2023-10-30T02:22:44Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vahdettin](https://avatars.discourse-cdn.com/v4/letter/v/e8c25b/32.png) [@Vahdettin](https://discourse.nodered.org/u/Vahdettin)\
**Post date:** [30 October 2023 02:22 UTC](https://discourse.nodered.org/t/notify-of-major-changes-to-collection/82455/1 "2023-10-30T02:22:45Z")

</div>

Hello, I have a collection I maintain that has a decent number of downloads. I have heard from a number of people that it's very useful but of course I don't know how many total there are. Either way, how do I notify current users that upgrading to a new version may break some things? If somebody never looks at the NPM or web-based Node-RED flows directory, that means they won't see the .MD file where I normally list out changes. Is there a way to drop a note that will appear next to the upgrade available note in the palette editor? Any way to warn people BEFORE they upgrade?

I do know how to generate a standard notification in the editor AFTER the upgrade but that is too late.

Any help appreciated.

Thanks,  
Vahdettin

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [30 October 2023 07:16 UTC](https://discourse.nodered.org/t/notify-of-major-changes-to-collection/82455/2 "2023-10-30T07:16:38Z")

</div>

The first thing is to make sure you increase the major revision number. That in itself implies breaking changes.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [30 October 2023 08:41 UTC](https://discourse.nodered.org/t/notify-of-major-changes-to-collection/82455/3 "2023-10-30T08:41:43Z")

</div>

> [@Vahdettin](#):
>
> Any way to warn people BEFORE they upgrade?

As mentioned by Colin, bump the Major for breaking changes and adhere to Semantic Versioning.  
Other ways to warn of breaking changes includes:

- Putting a Sticky on your repo
- Use these forums (Share your Nodes)

Sometimes it's also good to create a migration document, to help users migrate to the latest Major, I do this with my projects.

Another path, is to deprecate the area that is going to change, in a Minor update (allowing you to pre-warn users with a notification), I have corporate users, so often have to create a 'halfway house' release so to speak - given them time to make the required changes.

Honestly, as long as you follow best practices, you really can't baby users.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [30 October 2023 10:11 UTC](https://discourse.nodered.org/t/notify-of-major-changes-to-collection/82455/4 "2023-10-30T10:11:42Z")

</div>

And you can never have enough documentation. So making sure you update a comprehensive CHANGELOG. And to Marcus's point, you can include future breaking change warnings in there as well.

---

<div class="post-metadata">

**Author:** ![Vahdettin](https://avatars.discourse-cdn.com/v4/letter/v/e8c25b/32.png) [@Vahdettin](https://discourse.nodered.org/u/Vahdettin)\
**Post date:** [2 November 2023 03:13 UTC](https://discourse.nodered.org/t/notify-of-major-changes-to-collection/82455/5 "2023-11-02T03:13:07Z")

</div>

Hey, thanks for all the feedback. I guess the final answer is "no". I know some users of my collections are not necessarily programmer types and the concept of "major semver" is probably lost on them. I've also found that most of them do not participate in these forums.

I do see that a link to the Flows page is available next to the new version notification so I'll just hope they do that first as I have included the warnings in the MD file contents.

Thanks,  
Vahdettin

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [1 January 2024 03:13 UTC](https://discourse.nodered.org/t/notify-of-major-changes-to-collection/82455/6 "2024-01-01T03:13:34Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.