You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current behavior of the docs site will serve the tag with the most recent time attribute (src code) if no tag is provided in the URL params. My current understanding is that the time attribute is populated based on the latest push to the tag when the tag is indexed. It seems that once the tag has been initially indexed, the time will not be updated as the app will only reindex tags it has not seen before (src).
This means that repo owners do not necessarily control the ordering of the tags and the site will not always serve the latest version as indicated by semver. For example, currently the CAPI repo is serving v1.4.5 when no tag is provided in the URL params, despite the fact that v1.5.0 is the true latest.
This is a request to update the logic when no tag is provided in the URL params to prefer the latest tag by semver (if the repo's tags adhere to semver), rather than the time attribute from the tags relation in the doc db.
The text was updated successfully, but these errors were encountered:
The current behavior of the docs site will serve the tag with the most recent
time
attribute (src code) if notag
is provided in the URL params. My current understanding is that thetime
attribute is populated based on the latest push to the tag when the tag is indexed. It seems that once the tag has been initially indexed, thetime
will not be updated as the app will only reindex tags it has not seen before (src).This means that repo owners do not necessarily control the ordering of the tags and the site will not always serve the latest version as indicated by semver. For example, currently the CAPI repo is serving
v1.4.5
when notag
is provided in the URL params, despite the fact thatv1.5.0
is the truelatest
.This is a request to update the logic when no tag is provided in the URL params to prefer the latest tag by semver (if the repo's tags adhere to semver), rather than the
time
attribute from thetags
relation in thedoc
db.The text was updated successfully, but these errors were encountered: