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.

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

Update to latest vscode-quarkus and vscode-microprofile vsix extensions in Che (and CRW) #21172

Closed
nickboldt opened this issue Feb 16, 2022 · 1 comment
Labels
area/plugin-registry kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@nickboldt
Copy link
Contributor

nickboldt commented Feb 16, 2022

Is your task related to a problem? Please describe

In CRW-2662, publishing to download.jboss.org is going to stop being possible.

Therefore we need to move the build process where possible to push to openvsx or GH releases, and use those new URLs in Che and CRW plugin/devfile registies/sample projects.

Describe the solution you'd like

@rgrunber has suggested that it's probably safe to move up to the latest versions of:

and

See also camel-tooling/camel-lsp-client-vscode#910

Describe alternatives you've considered

No response

Additional context

No response

@nickboldt nickboldt added kind/task Internal things, technical debt, and to-do tasks to be performed. area/plugin-registry labels Feb 16, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Feb 16, 2022
@tolusha tolusha added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Feb 17, 2022
@che-bot
Copy link
Contributor

che-bot commented Aug 16, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 16, 2022
@che-bot che-bot closed this as completed Aug 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugin-registry kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

3 participants