Versioned docs are referring to assets in "latest" #207
Comments
jawnsy
added a commit
that referenced
this issue
Jun 13, 2023
Something is broken with our build, where mike is not correctly updating the assets stored in latest (#206) and the versioned docs are referring to assets in latest (#207) instead of the assets in the same version. To work around this for now, this change manually synchronizes changes using: cp -rf 2.10.13/assets/ latest/ cp -rf 2.10.13/img/ latest/
jawnsy
added a commit
that referenced
this issue
Jun 13, 2023
Something is broken with our build, where mike is not correctly updating the assets stored in latest (#206) and the versioned docs are referring to assets in latest (#207) instead of the assets in the same version. To work around this for now, this change manually synchronizes changes using: cp -rf 2.10.13/assets/ latest/ cp -rf 2.10.13/img/ latest/
|
This issue is possibly related to #81 |
|
Mike plugin has plans to fix. My attempt was unsuccessful. Will continue to manually copy latest version to latest. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our versioned docs are attempting to load an image from
latest, but due to #206, it does not exist there. This is a related but separate issue, as the versioned docs should be fully self-contained (only refer to content within the same folder), otherwise, old versions of our docs can change unexpectedly.The text was updated successfully, but these errors were encountered: