fix(v1): Fix v1 site deployment with Crowdin again...#4410
Merged
Conversation
|
[V1] Deploy preview success Built with commit 6ce721f |
|
Deploy preview for docusaurus-2 ready! Built with commit 6ce721f |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4410--docusaurus-2.netlify.app/classic/ |
|
Size Change: 0 B Total Size: 567 kB ℹ️ View Unchanged
|
This was referenced Mar 17, 2021
Closed
Closed
Closed
Merged
This was referenced Mar 17, 2021
Merged
Closed
Closed
Closed
Closed
Closed
mrizwanashiq
pushed a commit
to mrizwanashiq/docusaurus
that referenced
this pull request
Jun 25, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Motivation
Follow-up of #4396
This PR is a little refactor and mostly used to trigger a v1 site build on CircleCI...
Crowdin has a weird behavior on our v1 site and refuse to upload new versioned source files (even if you use a random filename + random file content).
The workaround is... to upload the files through their UI...
For some reasons, our v2 deployment does not seem affected by this issue.
I've reported the issue to their support, hopefully, they'll be able to fix this.
Note: it's important that all files are uploaded to crowdin otherwise the localized v1 site has missing pages and broken links on localized sites (ie the latest version is not included in the localized sites)