Pierre Vanduynslager

> Isn't basic auth this https://x-access-token: < GH_TOKEN>@github.com/owner/repo.git? yes it is. So? I don't understand what you are asking.

I can look at it. But some guidance would be welcomed!

If anyone's interested I published [karma-jasmine-jquery](https://github.com/vanduynslagerp/karma-jasmine-jquery). The package has no dependencies and let you choose your version of `jasmine-core` `karma-jasmine` `jasmine-jquery`.

semantic-release consider only the branches that exists on the remote repo. I'm guessing you don't have any branch on your remote that match that pattern.

I think that will be possible with the plugin architecture of #484. That would require to: - Modify https://github.com/semantic-release/commit-analyzer or create a new plugin that would return a list of...

Unfortunately none of the maintainer knows monorepo solutions enough to be able to come up a comprehensive design. In order to move forward we would like to have a proposal,...

Each commit might impact multiple module in the monorepo. semantic-release has to figure out which module has to be release and with what type of release, then release each one...

> The benefit of this solution is that it is simple and the semantic-release runs can be run in isolation as parallel jobs in CI (as it is usually done...

@evocateur nice to see you here! After reading a lot about multi-package repo, here what's missing in `semantic-release` so far: - Loop over the different packages directory and do the...

Nice to see that the Jest team is interested in semantic-release! > One thing I like about current lerna publish is that it also bumps dependents of updated packages. While...