V3.1.0 touching .config.nodes.json

It seems that node red 3.1.0 touches .config.nodes.json (so changes its timestamp) at each node red restart. This causes my backup strategy to keep backing it up. I believe that this is a change with 3.1.0. If so, was it intentional or a side effect of another change?

1 Like

Not intentional - it shouldn't be touching the file if the contents hasn't changed.

I have submitted an issue.

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