Gregor Martynus
Gregor Martynus
### The plan Migrate `semantic-release` and all the core plugins to native ES Modules. ### The motivation Node is moving to native ES Modules, so it's only a matter of...
🚧 ESM
I'm using this pull request to asses if moving to ESM is doable as part of v18. Still working through it
First stab to address #1370
If you use the semantic-release CLI to setup `semantic-release` in a GitHub repository, then you probably receive an E-Mail from GitHub with the subject "[GitHub] Deprecation Notice", stating that >...
``` $ npm_config_loglevel=verbose semantic-release-cli setup verb semantic-release Detected git url: https://github.com/eHealthAfrica/kazana-account-app.git ? Is the GitHub repository private? No ? What is your npm registry? https://registry.npmjs.org/ ? What is your npm...
At our organization, we use a dedicated CI GitHub user with restricted rights for semantic-release. The problem is that setup will fail if I select Travis in the setup, because...
as part of that, enable testing in Mac OS and Windows which currently fail because of flaky tests of the throttling code: https://github.com/semantic-release/github/pull/298/checks?check_run_id=1397908452
fixes #418 closes #330, closes #358, closes #390, closes #395, closes #396 For reference, because it came up in other discussions, here is how I replaced `proxyquire` with `quibble` ```diff...
Part of our efforts to migrate `semantic-release` to native ES Modules: https://github.com/semantic-release/semantic-release/issues/2133
This is a follow up to #268. We might want to remove `GITHUB_API_URL` from the README.md, and just handle it internally?