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

Remove support for win32-ia32 #1074

Open
felipecrs opened this issue Dec 30, 2024 · 5 comments
Open

Remove support for win32-ia32 #1074

felipecrs opened this issue Dec 30, 2024 · 5 comments
Labels
cli Component: cli

Comments

@felipecrs
Copy link
Contributor

Support for win32-ia32 target was removed from vsce a long time ago. I wonder if it should not be removed from ovsx too.

@amvanbaren amvanbaren added the cli Component: cli label Jan 13, 2025
@amvanbaren
Copy link
Contributor

ovsx uses vsce to package extensions (where target is used). ovsx doesn't validate the target, just passes it to vsce, so ovsx also doesn't support win32-ia32.

@amvanbaren
Copy link
Contributor

There are some extensions that support win32-ia32. Last publish was a year ago. @kineticsquid @tfroment Do you want to keep win32-ia32 (Windows 32-bit) support?

win32-ia32.csv

@kineticsquid
Copy link
Contributor

I'd venture that Microsoft might have other reasons for removing the support from the VS Code Marketplace. I'm not sure I fully understand the pros and cons on this one. Does it cost anything to keep it? What happens to these extensions should we remove it?

@felipecrs
Copy link
Contributor Author

I personally just think it's pointless to keep code and support for something that can't even be published anymore given vsce no longer supports it. So, my point is about code cleanup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli Component: cli
Projects
None yet
Development

No branches or pull requests

3 participants