-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
New release with updated dependencies #1231
Comments
Hey! Working on it, as you saw. Working on 100s of repos. I’ll close this for now, it’s not beneficial to have separate issues in some repos open. I don’t understand why Nuxt results in an error. With semver, you shouldn’t get a newer micromark that doesn’t work with current remark. |
This comment has been minimized.
This comment has been minimized.
I thought a new release might be easy to do - so sorry for the added noise. The problem in the context of nuxt/content is that some other packages depend on micromark 4 while this package here still uses v3, and nuxt has some troubles with these double versions. |
no problem about the issue/“noise”, it’s just easier for me to not try and track a couple issues scattered across different projects! The release is ready, it’s just that I also want to release a couple remark plugins that deeply integrate with this at the same time. And that I don’t have much time this weekend. Should be monday.
Ah. Hmm. Weird! |
@wooorm Is this related to the issue I am getting here?
|
I am getting it for seemingly every plugin. |
|
Yes, it is related. Wait a bit for me to update everything. Should be done in 2 weeks. |
Initial checklist
Problem
Using this package via nuxt/content results in some issues since the last released version depends on older version of dependencies, see nuxt/content#1562.
Solution
Should be resolved by 943f6ac, so only thing needed is a new release 😄
Alternatives
Couldn't find a workaround.
The text was updated successfully, but these errors were encountered: