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

Upgrade Hugo to 0.111.1 and fix doc issues #2455

Merged
merged 2 commits into from
Mar 6, 2023

Conversation

chalin
Copy link
Contributor

@chalin chalin commented Mar 6, 2023

  • Closes Bump hugo-extended from 0.110.0 to 0.111.1 #2452
  • Upgrades to Hugo 0.111.1
  • Fixes a bug in a page that was missing an end-tag marker for a shortcode
  • Fixes YAML sample in 2022 blog since some of the content is meant to be in comments (and otherwise results in pretty-printed YAML).
  • Drops unnecessary quotes around shortcode arguments

The only changes to the generated site files, other than the updated Hugo version, are due to pretty-printer changes and the YAML fragment update:

$ (cd public && git diff -bw --ignore-blank-lines -I "Hugo 0\.") | grep ^diff | grep -v \.xml
diff --git a/blog/2022/k8s-otel-expose/index.html b/blog/2022/k8s-otel-expose/index.html
diff --git a/docs/demo/services/shipping/index.html b/docs/demo/services/shipping/index.html

@chalin chalin added dependencies Pull requests that update a dependency file cleanup/refactoring labels Mar 6, 2023
@chalin chalin requested review from a team as code owners March 6, 2023 19:45
@chalin chalin requested a review from a team March 6, 2023 19:45
@chalin chalin requested review from a team as code owners March 6, 2023 19:45
@@ -8,7 +8,7 @@ aliases: [/python, /python/metrics, /python/tracing]
weight: 22
---

{{% lang_instrumentation_index_head "python" %}}
{{% lang_instrumentation_index_head python /%}}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note the missing "/" at the end here.

email: <REPLACE: your e-mail address, e.g.: "someone@example.com">
email: your-email-address-here@example.com # REPLACE
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The <REPLACE: your ...> (used here and two places below), confused even Prettier. This way of illustrating an entry that has parts to be replaced seems better / less confusing for the pretty-printers.

@cartermp cartermp merged commit 0a1be84 into open-telemetry:main Mar 6, 2023
@chalin chalin deleted the chalin-im-hugo-0.111.1 branch March 7, 2023 00:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup/refactoring dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants