dmeents / semantic-release-yarn Goto Github PK

I've just migrated from semantic-release-npm, it would be nice if the package was able to resolve registry from npmScopes declared in the .yarnrc.yml file. Reading registry from the publishConfig.registry field to the package.json creates redundant configuration.

With npmScopes set up in either .yarnrc.yml or in ci workflow files, does the semantic-release-yarn plugin even need to resolve and overwrite the registry?

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

• chore(deps): update dependency @dmeents/semantic-release-yarn to v1

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update yarn to v4
• fix(deps): update dependency @semantic-release/error to v4

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

The script does not appear to be run for the correct workspace in monorepo setups. Does the plugin intend to handle monorepos?

web-player-shared does not have private: true declared in its package.json.

In monorepos, the root directory package.json should have private: true declared, but each separate workspace package does not. Running yarn npm publish locally in the correct folder works.

Hello,

in our company we are using Microsoft Azure DevOps and just upgraded to yarn v3. Since you wrote this library you know why we need it! Thanks for it.

Sadly, Microsoft Azure DevOps doesn't allow creation of npmToken. We just don't have that value. In Microsoft, we can just create npmAuthIdent.

It would be really good if we could add functionality to allow also authentication with npmAuthToken

For this I have created a PR that I will link!

Hi there,

First of all, I would like to thank you for this great plugin you did, thanks a lot!

So to the point, Today I upgraded yarn to latest version (4.0.2) and as part of the breaking changes included in the release, there is one that is breaking semantic-relase-yarn, which is that all the native plugins are now included by default, so when it tries to install it, it breaks saying the following:

A plugin named @yarnpkg/plugin-version is already installed; possibly attempting to import a built-in plugin.