Allow configuration through config file or a vsce key under package.json #548
Assignees
Labels
feature-request
Request for new features or functionality
help wanted
Issues identified as good community contribution opportunities
released
Milestone
Comments
joaomoreno
added
feature-request
|
🎉 This issue has been resolved in version 2.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
felipecrs
added a commit
to felipecrs/semantic-release-vsce
that referenced
this issue
Jan 18, 2022
As `vsce` now supports configuration through the `package.json` file (see microsoft/vscode-vsce#548), this option was dropped to simplify the codebase. One should either rely on the `vsce` automatically detecting when to use `yarn` (see microsoft/vscode-vsce#480), or add the following to `package.json`: ```json { "vsce": { "yarn": true } } ```
felipecrs
added a commit
to felipecrs/semantic-release-vsce
that referenced
this issue
Jan 18, 2022
As `vsce` now supports configuration through the `package.json` file (see microsoft/vscode-vsce#548), this option was dropped to simplify the codebase. One should either rely on the `vsce` automatically detecting when to use `yarn` (see microsoft/vscode-vsce#480), or add the following to `package.json`: ```json { "vsce": { "yarn": true } } ```
felipecrs
added a commit
to felipecrs/semantic-release-vsce
that referenced
this issue
Jan 18, 2022
As `vsce` now supports configuration through the `package.json` file (see microsoft/vscode-vsce#548), this option was dropped to simplify the codebase. One should either rely on the `vsce` automatically detecting when to use `yarn` (see microsoft/vscode-vsce#480), or add the following to `package.json`: ```json { "vsce": { "yarn": true } } ```
felipecrs
added a commit
to felipecrs/semantic-release-vsce
that referenced
this issue
Jan 18, 2022
As `vsce` now supports configuration through the `package.json` file (see microsoft/vscode-vsce#548), this option was dropped to simplify the codebase. One should either rely on the `vsce` automatically detecting when to use `yarn` (see microsoft/vscode-vsce#480), or add the following to `package.json`: ```json { "vsce": { "yarn": true } } ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the configuration can be done through CLI options, such as
--yarnand--github-branch. It would be very good if configurations could be done through thepackage.json, as is fornpm publishitself. Something like:{ "name": "vscode-shellcheck", [...] "vsce": { "yarn": true, "githubBranch": "main" } }This would be especially useful in
semantic-release-vsce, as it currently does not allow the user to set extra arguments for thevscecall.felipecrs/semantic-release-vsce#115
The text was updated successfully, but these errors were encountered: