Benoit Averty

I would but unfortunately I don't publish with npm. My build script is executed way before the semantic release.

The problem with all these solutions is that I need to have two configurations : One that outputs the version or sets it somewhere, and one for the actual release...

I will try to be more detailed about my workflow. I have a Gitlab-CI pipeline that does this jobs in order : ``` 1) Build my application (npm run build...

I can't use this workflow unfortunately. My project is not a NPM library and it's not released on any NPM registry. My real artifact is a docker image. Moreover, the...

@jhabdas I tried other libs but semantic-release is the only one that is this high-level. I thought it would be less work to implement the compte workflow (parse commits, determine...

> Counter argument to this behavior: if you accidentally make a breaking env var change, not instantly deploying it gives you time to catch that (example: git commit vs git...

I found the same thing as @asgarddesigns. However, it is still related to the import not being used because adding a reference to the unused import fixed the problem.

The `--clearmodifiers` solution has the same problem as what I currently have I think. I have to release alt to press it again if I want to type End then...

This is the config I use to start the selenium standalone service in local only : `services: ci ? ['sauce'] : ['selenium-standalone']` the ci var is defined as `const ci...

I would also like to see this fixed :)