Rafal Drozda

> But the original was about updating the integrated dashboard. And i'm not quite sure if this is solved already. Yes, i did not specifically define a version of the...

> I was kindof thinking the other direction leveraging existing versioning system. By (semi) automating new releases. By that I mean a dependabot ( like) system that automatically creates pull-requests...

> What do you mean by comment. The changelog in the README? > Anyways, first things first: Working on the dashboard dependency change. no I mean in the git comment...

> > * package.json > > * io-package.json (including news) > > * package-lock.json > > * readme > > > > are update accordingly > > hm, i don't...

just thinking a little more around that, for now that's maybe even the most easiest solution as local the data can be updated and also release script used which handle...

> > what do you think? Continue looking for solution as action or local NodeJS proces ? > > > > Agree, > > existing Action base is probably not...

> Wouldn't it be enough to "just" update the dashboard dependency, add info to readme and then run `release-script` doing it locally yes, release script will take care of all...

> > > Wouldn't it be enough to "just" update the dashboard dependency, add info to readme and then run `release-script` > > > > > > doing it locally...

> Thinking a bit more... something else. Have to handle / deal with existing stuff in the "Worl in progress" section in the readme. Probably just temporarily remove it and...

> So the initial state of the README for the update-script would be: > > ```md > > ## Changelog > > > > > > ### 0.4.1 (2023-11-05) >...