-
Notifications
You must be signed in to change notification settings - Fork 5
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
chore: also run ecosystem ci on windows #15
base: main
Are you sure you want to change the base?
Conversation
thank you! if any of these are reproducible in the moduleβs main repo we should probably add a windows workflow there as well |
I can at least reproduce the issue coming from |
indeed I could β¦ just not sure how welcome it would be π |
Happy to do it, but I think we should
|
π Linked issue
β Type of change
π Description
Sometimes I run in errors that are specific to windows. Perhaps this is because most of the core developers in the nuxt ecosystemu seem to use linux/macos and the ci tests in the repos are also usually only run on ubuntu.
It would be nice if such errors could be discovered before and not after a new release of a module/nuxt version. For this reason, we activate the ci-ecosystem tests also on windows.
Test run (3.x branch): https://github.com/tobiasdiez/ecosystem-ci/actions/runs/11026454120
Test run (main branch): https://github.com/tobiasdiez/ecosystem-ci/actions/runs/11026329086
There are a few modules that are indeed broken on Windows (but not on ubuntu). Most of these issues seem to be due to nuxtlabs/nuxt-component-meta#72.