Closed abbycar closed 8 months ago
Hello! Yes this is expected since we have released a newer version for Docusaurus v3. But we are going to do this as soon as possible.
On Fri, 17 Nov 2023 at 8:16 PM, Abby Carey @.***> wrote:
We just upgraded to Docusaurus v3 and can't get terminology to work. :( Is this a known issue?
— Reply to this email directly, view it on GitHub https://github.com/grnet/docusaurus-terminology/issues/24, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAF7A4H2YWQZ5KGSOMWFGHDYE6SZDAVCNFSM6AAAAAA7QFQRISVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4TSNRYGQYTQOI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
You have released a newer version? Where is it?
There is no release available supporting Docusaurus v3 yet. Feel free to submit a Pull Request with any changes needed in the codebase.
Is there a release yet?
Same here, would be great!
@tsironis I have an open pull request upgrading some of the components: #25
The major issue seems to be a dependency that doesn't seem to be actively maintained anymore: https://github.com/timc1/postel
Let's put this a priority for the next week, @VasiaKoum.
@philippnagel it seems easy enough to replace with something newer and/or better maintained.
You may use the v2.0.0-rc release candidate version. The stable v2.0.0 will follow in the next few days.
We just upgraded to Docusaurus v3 and can't get terminology to work. :( Is this a known issue?