Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support for packagePath and version options together #261

Closed
ivanovit opened this issue May 9, 2018 · 1 comment
Closed

Support for packagePath and version options together #261

ivanovit opened this issue May 9, 2018 · 1 comment
Assignees
@joaomoreno
Labels
feature-request Request for new features or functionality help wanted Issues identified as good community contribution opportunities

Comments

@ivanovit
Copy link

ivanovit commented May 9, 2018 •
edited

Currently, when both options are provided we got the following error: Not supported: packagePath and version.

We have internal builds and we use pre-release part of the version for build information. We want to remove the pre-release part from a version before publishing specific .vsix that has been tested without rebuilding the package.

Could you add support to change only the version before publishing specific .vsix?
@ivanovit ivanovit changed the title feature: Add support for both packagePath and version options feature: Add support for packagePath and version options together May 9, 2018
@joaomoreno joaomoreno added this to the Backlog milestone May 28, 2018
@joaomoreno joaomoreno added the help wanted Issues identified as good community contribution opportunities label May 28, 2018
@joaomoreno joaomoreno added the feature-request Request for new features or functionality label Sep 20, 2018
@joaomoreno joaomoreno removed this from the Backlog milestone Oct 11, 2019
@joaomoreno joaomoreno changed the title feature: Add support for packagePath and version options together Support for packagePath and version options together Oct 27, 2021
@joaomoreno
Copy link
Member

With #596, you will be able to publish using --no-update-package-json. This means you can provide any version at publish time and that will work in-memory: you don't have to change package.json beforehand.

@joaomoreno joaomoreno self-assigned this Nov 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joaomoreno joaomoreno

Labels
feature-request Request for new features or functionality help wanted Issues identified as good community contribution opportunities
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@joaomoreno @ivanovit