question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Version header is h3 instead of h2 when header has a compare link

See original GitHub issue

After creating a new repo and running standard version twice the header for the version line is h3 instead of h2, like the following example.

# Changelog

All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.

### [1.1.1](///compare/v1.1.0...v1.1.1) (2019-10-25)

## 1.1.0 (2019-10-25)


### Features

* a commit 6dbf7a9

You can reproduce this issue by running the following

mkdir foo
cd foo
npm init -y
npm install -D standard-version
git init
echo -e "node_modules" > .gitignore
git add package.json
git commit -m "feat: a commit"
standard-version
cat CHANGELOG.md
// here the changelog will have a line like
// ## 1.1.0 (2019-10-25)
// with h2, the expected result

standard-version
cat CHANGELOG.md
// here the changelog will have a line like
// ### [1.1.1](///compare/v1.1.0...v1.1.1) (2019-10-25)
// with h3, which isn't the expected result, it should be h2

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

3reactions
negebauercommented, Nov 8, 2019

and by the way, why is it h3 for patches? I thought this was based on keepachangelog which users h2 for all versions

2reactions
Yogucommented, Sep 6, 2022

and by the way, why is it h3 for patches? I thought this was based on keepachangelog which users h2 for all versions

Agree, this is really weird because

  • the types like “Bugfixes” are now on the same level as the versions
  • patches appear as subheadings of the next minor/major release. If the last release is a patch release, a heading level is missing.

To me, the result just looks broken

Read more comments on GitHub >

github_iconTop Results From Across the Web

Google Explains How to Use Headings for SEO
Google's John Mueller explains the proper use of heading elements (H1, H2, H3) for SEO.
Read more >
Header Tags: A Simple (But Complete) Guide To H1, H2 ...
In this new guide, you'll learn exactly how to use H1 to H6 heading tags to optimize your page and drive higher search...
Read more >
Headings | Web Accessibility Initiative (WAI)
Heading ranks. Exception for fixed page sections · Organize passages of text · Headings that reflect the page organization. Main heading before navigation;...
Read more >
Using H3 before or instead of an H2... | SEO Forum
My designer and I have been having an argument: we have a blog with short, 400 words posts. They have an H1 with...
Read more >
<h1>–<h6>: The HTML Section Heading elements
A page should generally have a single <h1> element that describes the ... <h1>Heading level 1</h1> <h2>Heading level 2</h2> <h3>Heading ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found