-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove tarballs & Docker links for v20.2 and below #19036
base: main
Are you sure you want to change the base?
Remove tarballs & Docker links for v20.2 and below #19036
Conversation
Files changed:
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify site configuration. |
@mdlinville maybe this is also an offline convo but wanted to show you what i have so far to get your feedback from a tools POV in fact let me DM you to set up some time to walk through this PR maybe |
b71b6bc
to
f703a09
Compare
@jlinder and @celiala i believe this PR implements the "remove binaries, tarballs, and Docker links for <= v20.1" as we discussed in our meeting See the PR summary for details of how this is accomplished by adding a new variable to each block of the the rest of the edits beyond the Liquid templates and the YAML file are removing links from old release pages probably a good place to start verifying the expected behavior is the rendered previews linked from the description |
cc @jaiayu FYI just so you know this is in progress |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The approach LGTM. Maybe I am missing it but I can't see the logic where you are using the new field from the YAML.
Yayyyy thanks for the review Matt!!!! the logic is here (and also in several other places but they're all the same basic Liquid code): it basically adds another case to the existing if-else blocks below the "is this a cloud-only release" check with another check that is basically "is this release no longer downloadable" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the releases that are being suppressed (20.1 and before) this LGTM. But the v20.2 releases also need to have their tarballs and docker links removed as well (somehow we must have missed clearly indicating the 20.2 releases also needed to be included when we discussed this change 😕).
Fixes DOC-11092 Summary of changes: - Update releases.yml with a new boolean field - Update releases index page to stop showing downloads for versions <= v20.2 - Update individual release pages to remove download links for versions <= v20.2 How it works: When a specific release (or an entire major version's releases) should be made no longer available for download, add the following k-v pair to the YAML block for that release: is_not_downloadable: true There is now logic in the Liquid templates that build the main releases page that checks for this YAML key being set to true. If it is set to true, the releases page will no longer display links to: - Pre-built binary downloads - Docker tags - Release tarballs Instead, the table cells where such artifacts used to appear will now display the message: No longer available for download.
f703a09
to
950c324
Compare
Remove v20.2 tarballs and Docker links as well
@jlinder just updated to remove v20.2 as well, sorry about the confusion on my end, classic off-by-one error i guess PTAL! |
Fixes DOC-11092
Summary of changes:
Update releases.yml with a new boolean field
Update releases index page to stop showing downloads for versions <=
v20.2
Update individual release pages to remove download links for versions
<= v20.2
How it works:
When a specific release (or an entire major version's releases) should
be made no longer available for download, add the following k-v pair to
the YAML block for that release:
There is now logic in the Liquid templates that build the main releases
page that checks for this YAML key being set to true. If it is set to
true, the releases page will no longer display links to:
Instead, the table cells where such artifacts used to appear will now
display the message: