Marc Bernard

We have https://github.com/verdaccio/verdaccio/blob/master/docs/migrations-guide.md but consolidating it to `MIGRATE.md` makes sense.

Sometimes there are difficulties that packages are not visible. So getting the secret migration right, is important. It's a combo with a node upgrade and tricky. On a side note,...

I think this is it: https://help.sap.com/doc/abapdocu_latest_index_htm/latest/en-US/index.htm?file=abennews-756-dref.htm

I'm not sure how you want to deal with the lint issue. It's the nature of the test to include Unicode characters. Add it as an exception?

I made a mistake making changes directly to the master of my fork. I added the serialize part. I will run some tests this week. FYI, the use case is...

Going for the 3rd solution would be a big change since all methods taking a path would need to be updated for minimal benefit. I fixed a bug when several...

Much of my apm code is now public. All the dependency sections of package.json have this key/value format (`"lodash": "^4.17.0") so it's quite common. Here's how I convert these to...

With the draft, `premajor`, `preminor`, `prepatch` do two things to the pre-release: 1. add a new pre-release 0, if it does not exist 2. increases the pre-release id, if it...

I would use the new `release` to exit pre-release mode, and then use the existing `premajor/minor/patch` to get into a new pre-release. That's a clear separation of functionality.

After `release`, we have a semver (no pre-release). So any `premajor/minor/patch` will increase the version.