Skip to content
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

Compatibility challenges with Hugo 0.6.x #20335

Closed
85 of 100 tasks
sftim opened this issue Apr 14, 2020 · 4 comments
Closed
85 of 100 tasks

Compatibility challenges with Hugo 0.6.x #20335

sftim opened this issue Apr 14, 2020 · 4 comments
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@sftim
Copy link
Contributor

sftim commented Apr 14, 2020

Problem:
The existing content is not completely compatible with the 0.6x.x releases of Hugo. Hugo 0.60.0 became compatible with CommonMark. Some existing content doesn't render the same way with Hugo < 0.60.0 as it does with Hugo ≥ 0.60.0

This is a tracking issue and will track at least the top 100 most commonly visited pages on this site.

Top 100 pages to check:

Legend

Checked items have been reviewed
⚠️ = needs attention

Additional Information:
This issue heavily draws on work started in PR #19907 (thanks @jimangel!)

#19028 (comment) captures more detail
/kind cleanup
/priority important-longterm

@sftim
Copy link
Contributor Author

sftim commented May 26, 2020

I've gone through the top 100 pages and checked the ones that already work fine.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 24, 2020
@sftim
Copy link
Contributor Author

sftim commented Aug 24, 2020

I think these are largely dealt with.
/close

@k8s-ci-robot
Copy link
Contributor

@sftim: Closing this issue.

In response to this:

I think these are largely dealt with.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

3 participants