Skip to content

fix regression with header links

Michael Friedrich requested to merge fix-regression-url-anchors-pin-google-docsy-0-8-0 into main

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

We recently updated the Hugo module dependencies to include fixes for slow CI/CD pipelines, and other fixes from the docsy-theme. Running hugo mod all -u pulled in a new dependency with google/docsy 0.9.0. This seems to be a major release with breaking changes for the gitlab theme, and URL anchor rendering. More analysis in #194 (closed)

This MR pin the Hugo module dependency to 0.8.0 which fixes the regression for the moment, until we figure out a proper fix for 0.9.0 compatibility.

The process of updating and testing Hugo modules and dependencies is not documented yet - will be done in docsy-gitlab#4 (closed)

  • Hugo: Pin google/docsy 0.8.0 to fix regression with URL anchor rendering

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Merge request reports