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

Use correct heading level in changelog (in release branch 2.3.x) #3283

Merged
merged 1 commit into from May 31, 2021

Conversation

erimatnor
Copy link
Contributor

The 2.3.0 release used the wrong heading level. Fix it for future
releases.

The 2.3.0 release used the wrong heading level. Fix it for future
releases.
@erimatnor erimatnor requested a review from a team as a code owner May 26, 2021 11:55
@erimatnor erimatnor requested review from pmwkaa, afiskon and mfundul and removed request for a team May 26, 2021 11:55
@erimatnor erimatnor self-assigned this May 26, 2021
@codecov
Copy link

codecov bot commented May 26, 2021

Codecov Report

❗ No coverage uploaded for pull request base (2.3.x@13081f1). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##             2.3.x    #3283   +/-   ##
========================================
  Coverage         ?   90.45%           
========================================
  Files            ?      216           
  Lines            ?    35986           
  Branches         ?        0           
========================================
  Hits             ?    32552           
  Misses           ?     3434           
  Partials         ?        0           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 13081f1...d188c65. Read the comment docs.

@erimatnor erimatnor merged commit fe8910e into timescale:2.3.x May 31, 2021
@erimatnor erimatnor deleted the fix-changelog-heading-2.3.x branch May 31, 2021 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants