search

AlCalzone / release-script

Painless release management for Node.js projects
MIT License
14 stars 10 forks source link

io-package.json is not updated anymore? #127

Closed SKB-CGN closed 2 years ago

SKB-CGN commented 2 years ago

Hi, i did some changes to my project and the io-package.json is not updated with the new text from README.md.

When uploading them to Github, the Test and Release Runs fail due to version mismatch.

AlCalzone commented 2 years ago

You probably upgraded to v3 and didn't read the changelog?

https://github.com/AlCalzone/release-script#plug-ins

You'll have to install and enable the iobroker plug-in for this to work.

SKB-CGN commented 2 years ago

Perhaps, this came from the "dependabot"-checks.

Now, its half working.

I get this error: commit:package [ERR] Updating lockfile failed: npm ERR! code ETARGET npm ERR! notarget No matching version found for @alcalzone/release-script-plugin-license@3.0.0. npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn't exist. npm ERR! notarget npm ERR! notarget It was specified as a dependency of 'iobroker.wallbox' npm ERR! notarget

SKB-CGN commented 2 years ago

After changing the version to 3.5.9 it is working again.

Could it be the reason, that "dependabot" changed my package.json file?

AlCalzone commented 2 years ago

Yeah it's possible. You should review the changes it does though.

At least with the default configuration contained in the adapter template, major updates aren't merged automatically since they can contain such breaking changes.