update docusaurus version to fix ssl algo error #525
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@maks thanks for trying to review this, for some reason some actions started to act up all together and I plan to review and have your update live |
|
@leoafarias thanks for chasing it up and fixing the config 👍🏻 the latest CI run seems to have deployed the docs successfully. 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@leoafarias This is an attempt to fix the failure of the documentation deployment action: https://github.com/fluttertools/fvm/actions/runs/4713405556/jobs/8359082936
According to the comment on the docusaurus issue a combination of using the latest version of docusaurus plus regenerating the yarn lock file to ensure version 5.5 or newer of webpack is used should fix the underlying issue, more details about which are on this SO thread.
Unfortunately I can't easily test this myself as the Github action for deploying the docs is obviously set to only run on merges into
main