Update workflow is inconsistent with latest version and alias #206
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/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When
mikeran to update2.10.13andlatest, the updates made to both folders seems different for some reason: #196The 2.10.13 version has all the assets updated, as we'd expect:
The
latestalias version does not touchassets, and it's not clear why this would be different (I'd have expected the contents of2.10.13andlatestto be identical):The text was updated successfully, but these errors were encountered: