Again! Fix the failed CI

[fritx]

✅ CI is now passing again:
https://github.com/fritx/nue/actions/runs/8000550563
https://github.com/fritx/nue/actions/runs/8000785880

1. Attempt to pass the CI by handling missing pubDate while sorting
2. Attempt to pass the Windows CI by adapting dir path
3. Attempt to pass the (Node) CI by replacing import.meta.resolve
   • Tried import.meta.resolve iwth both Node@18.18 and Node@18.19.1 in CI but failed.
   • While running *.mjs with import.meta.resolve is fine with Node@18.19.1 locally. Any one knows why?
4. Attempt to pass the Windows CI by removing the leading slash from absolute path

• The logic appears in several places and can be extracted in the future, maybe next PR.

[fritx]

Oops. I guess CI failed here because of the latest GLOW-related commits.
You guys are commiting so fast 🚀 @tipiirai

[tipiirai]

Outch. I'll fix that

[tipiirai]

I just pushed a fix to glow test suite, but it's not passing here. I have updated the version number to 0.1.2. Is that the reason?

[fritx]

Outch. I'll fix that

I also had a fix on that in the context of another PR. - #215 (Looks equivalent!)
I'll try to rebase the latest master. Wait.

not passing here. I have updated the version number to 0.1.2. Is that the reason?

I'm not sure but it is prossible as we had the same confusion some time ago (CI not passing right after version bumping).

[fritx]

Now the PR is ready @tipiirai

[tipiirai]

Perfect. Thanks!