Skip to content

[vs code extension publishing] - Allow rush change and version policies to be separate from npm publishing#5504

New issue
New issue
Open
Open
[vs code extension publishing] - Allow rush change and version policies to be separate from npm publishing#5504
Labels
effort: easyProbably a quick fix. Want to contribute? :-)effort: mediumNeeds a somewhat experienced developerenhancementThe issue is asking for a new feature or design changeneeds designThe next step is for someone to propose the details of an approach for solving the problem
@TheLarkInn

Description

@TheLarkInn
TheLarkInn
opened on Dec 15, 2025

Currently today, if you tried to setup changefiles for our vs code extensions, it would attempt to publish these packages to npm.

To support our vscode extension change system, we want to be able to have changefiles and version policies without being tied to npm publishing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    effort: easyProbably a quick fix. Want to contribute? :-)effort: mediumNeeds a somewhat experienced developerenhancementThe issue is asking for a new feature or design changeneeds designThe next step is for someone to propose the details of an approach for solving the problem

    Type

    No type

    Projects

    Bug Triage

    Status

    General Discussions

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions