keep-a-changelog

If you build software, keep a changelog.

MIT License

Downloads
36
Stars
6.1K
Committers
122
keep-a-changelog - v1.1.1 — Many new translations, centralized links, and more Latest Release

Published by olivierlacan over 1 year ago

Added

  • Arabic translation (#444).
  • v1.1 French translation.
  • v1.1 Dutch translation (#371).
  • v1.1 Russian translation (#410).
  • v1.1 Japanese translation (#363).
  • v1.1 Norwegian Bokmål translation (#383).
  • v1.1 "Inconsistent Changes" Turkish translation (#347).
  • Default to most recent versions available for each languages
  • Display count of available translations (26 to date!)
  • Centralize all links into /data/links.json so they can be updated easily

Fixed

  • Improve French translation (#377).
  • Improve id-ID translation (#416).
  • Improve Persian translation (#457).
  • Improve Russian translation (#408).
  • Improve Swedish title (#419).
  • Improve zh-CN translation (#359).
  • Improve French translation (#357).
  • Improve zh-TW translation (#360, #355).
  • Improve Spanish (es-ES) transltion (#362).
  • Foldout menu in Dutch translation (#371).
  • Missing periods at the end of each change (#451).
  • Fix missing logo in 1.1 pages
  • Display notice when translation isn't for most recent version
  • Various broken links, page versions, and indentations.

Changed

  • Upgrade dependencies: Ruby 3.2.1, Middleman, etc.

Removed

  • Unused normalize.css file
  • Identical links assigned in each translation file
  • Duplicate index file for the english version
keep-a-changelog - 1.1.0 — Be careful about inconsistent changelogs

Published by olivierlacan almost 5 years ago

Added

  • New paragraph on the risks of inconsistent changelog (and releases) in the
    Bad Practices section from @RichardLitt
keep-a-changelog - 1.0.0 — 6 new translations, brand new identity, and more.

Published by olivierlacan over 7 years ago

Added

  • New visual identity by @tylerfortune8.
  • Version navigation.
  • Links to latest released version in previous versions.
  • "Why keep a changelog?" section.
  • "Who needs a changelog?" section.
  • "How do I make a changelog?" section.
  • "Frequently Asked Questions" section.
  • New "Guiding Principles" sub-section to "How do I make a changelog?".
  • Simplified and Traditional Chinese translations from @tianshuo.
  • German translation from @mpbzh & @Art4.
  • Italian translation from @azkidenz.
  • Swedish translation from @magol.
  • Turkish translation from @karalamalar.
  • French translation from @zapashcanon.
  • Brazilian Portugese translation from @Webysther.
  • Polish translation from @amielucha.
  • Russian translation from @aishek.
  • Czech translation from @h4vry.
  • Slovak translation from @jkostolansky.
  • Korean translation from @pierceh89.

Changed

  • Start using "changelog" over "change log" since it's the common usage.
  • Start versioning based on the current English version at 0.3.0 to help
    translation authors keep things up-to-date.
  • Rewrite "What makes unicorns cry?" section.
  • Rewrite "Ignoring Deprecations" sub-section to clarify the ideal
    scenario.
  • Improve "Commit log diffs" sub-section to further argument against
    them.
  • Merge "Why can’t people just use a git log diff?" with "Commit log
    diffs"
  • Fix typos in Simplified Chinese and Traditional Chinese translations.
  • Fix typos in Brazilian Portuguese translation.
  • Fix typos in Turkish translation.
  • Fix typos in Czech translation.
  • Fix typos in Swedish translation.
  • Improve phrasing in French translation.
  • Fix phrasing and spelling in German translation.

Removed

  • Section about "changelog" vs "CHANGELOG".
keep-a-changelog - 0.3.0 — Russian, Brazilian Portugese, Spanish translations.

Published by olivierlacan over 7 years ago

Added

  • RU translation from @aishek.
  • pt-BR translation from @tallesl.
  • es-ES translation from @ZeliosAriex.
keep-a-changelog - 0.2.0 — It's not just about open source

Published by olivierlacan over 7 years ago

Changed

  • Remove exclusionary mentions of "open source" since this project can
    benefit both "open" and "closed" source projects equally.
keep-a-changelog - 0.1.0 — Should you ever rewrite a change log?

Published by olivierlacan over 7 years ago

Added

  • Answer "Should you ever rewrite a change log?".

Changed

  • Improve argument against commit logs.
  • Start following SemVer properly.
keep-a-changelog - 0.0.8 — Fix factual error on date formats, typos, and erroneous links.

Published by olivierlacan over 9 years ago

Changed

  • Update year to match in every README example.
  • Reluctantly stop making fun of Brits only, since most of the world
    writes dates in a strange way.

Fixed

  • Fix typos in recent README changes.
  • Update outdated unreleased diff link.
keep-a-changelog - 0.0.7 — Acknowledge GNU change log style, point to ISO 8601, clean links.

Published by olivierlacan over 9 years ago

Added

  • Link, and make it obvious that date format is ISO 8601

Changed

  • Clarified the section on "Is there a standard change log format?"

Fixed

  • Fix Markdown links to tag comparison URL with footnote-style links.
keep-a-changelog - README section on 'yanked' releases.

Published by olivierlacan almost 10 years ago

Added

  • README section on "yanked" releases.
keep-a-changelog - Markdown links to tags on versions headings, unreleased section.

Published by olivierlacan almost 10 years ago

Added

  • Markdown links to version tags on release headings
  • Unreleased section to gather unreleased changes and encourage note
    keeping prior to releases.
keep-a-changelog - Remove empty sub-sections, differentiate between "CHANGELOG" and "change log"

Published by olivierlacan almost 10 years ago

Added

  • Better explanation of the difference between the file ("CHANGELOG")
    and its function "the change log".

Changed

  • Refer to a "change log" instead of a "CHANGELOG" throughout the site
    to differentiate between the file and the purpose of the file — the
    logging of changes.

Removed

  • Remove empty sections from CHANGELOG, they occupy too much space and
    create too much noise in the file. People will have to assume that the
    missing sections were intentionally left out because they contained no
    notable changes.
keep-a-changelog - "Why should I care?"

Published by olivierlacan almost 10 years ago

Added

  • "Why should I care?" section mentioning The Changelog podcast.
keep-a-changelog - Explain reverse chronological date ordering.

Published by olivierlacan almost 10 years ago

Added

  • Explanation of the recommended reverse chronological release ordering.
keep-a-changelog - Create initial CHANGELOG example.

Published by olivierlacan almost 10 years ago

Added

  • This CHANGELOG file to hopefully serve as an evolving example of a standardized open source project CHANGELOG.
  • CNAME file to enable GitHub Pages custom domain
  • README now contains answers to common questions about CHANGELOGs
  • Good examples and basic guidelines, including proper date formatting.
  • Counter-examples: "What makes unicorns cry?"
Package Rankings
Top 3.81% on Proxy.golang.org
Top 30.06% on Pypi.org
Badges
Extracted from project README
Keep a Changelog v1.1.0 badge Version 1.1.0 Badge MIT License Badge
Related Projects