keep-a-changelog
semver
keep-a-changelog | semver | |
---|---|---|
10 | 725 | |
5,924 | 7,037 | |
- | 0.8% | |
7.8 | 0.6 | |
10 days ago | 12 days ago | |
Haml | ||
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
keep-a-changelog
-
Common Changelog
A style guide for changelogs, adapted from and a stricter subset of [Keep a Changelog](https://keepachangelog.com/)
- How do you handle API documentation and change logs?
-
What is your favorite method to take internal notes/documentation about the projects you build?
not entirely related to your question, but worth a read : https://keepachangelog.com/
- The Subtle Art of the Changelog
-
Product development guide #1
A Changelog should be written for each release, conforming to the standard https://keepachangelog.com/
-
Git log is not a changelog
I agree, I used to have a NEWS file in my projects (later a NEWS.md), but as others commented, the signification of the term "changelog" has changed. Sites like https://keepachangelog.com/ really refers to release notes or news.
- How do you manage your changelog sections?
-
Ask HN: What Makes a Good Changelog?
Overall I like the format and advice from https://keepachangelog.com/
Weβve adopted it at work and itβs nice to have a consistent format that is relatively noise free.
-
Semantic Versioning and Changelog
You can read more about it at: https://keepachangelog.com/
-
What is a Changelog and how to write one?
# Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). ## [Unreleased] ## [0.0.4] - 2014-08-09 ### 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. ## [0.0.3] - 2014-08-09 ### Added - "Why should I care?" section mentioning The Changelog podcast. ## [0.0.2] - 2014-07-10 ### Added - Explanation of the recommended reverse chronological release ordering. ## [0.0.1] - 2014-05-31 ### Added - This CHANGELOG file to hopefully serve as an evolving example [Unreleased]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.0.4...HEAD [0.0.4]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.0.3...v0.0.4 [0.0.3]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.0.2...v0.0.3 [0.0.2]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.0.1...v0.0.2 [0.0.1]: https://github.com/olivierlacan/keep-a-changelog/releases/tag/v0.0.1
semver
-
Git commit helper: add emojis to your commits
Using Conventional Commits β as a standard for your commit messages, makes Semantic Versioning π as easy as can be, with tools like Conventional Changelog π Standard Version π and Semantic Release π¦π
-
Why write a library?
Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.
-
Node package managers (npm, yarn, pnpm) - All you need to know
npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.
-
Snyk CLI: Introducing Semantic Versioning and release channels
We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.
-
Master the Art of Writing and Launching Your Own Modern JavaScript and Typescript Library in 2024
Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.
-
Using semantic-release to automate releases and changelogs
Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH
-
Essential Command Line Tools for Developers
Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-releaseβ¦
-
Testing Our Tasks
The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?
-
What is Semantic Versioning and why you should use it for your software ?
For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org
-
Neovim v0.9.5 Released
I believe neovim follows semantic versioning. https://semver.org/
What are some alternatives?
conventional-changelog - Generate changelogs and release notes from a project's commit messages and metadata.
react-native - A framework for building native applications using React
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
semantic-release - :package::rocket: Fully automated version management and package publishing
git-quick-stats - ββ βββ Git quick statistics is a simple and efficient way to access various statistics in git repository.
Release It! π - π Automate versioning and package publishing
changesets - π¦ A way to manage your versioning and changelogs with a focus on monorepos
chronicle - a fast changelog generator sourced from PRs and Issues
helmfile - Deploy Kubernetes Helm Charts
tag - Git utility to create tags in order to identify specific releases
Poetry - Python packaging and dependency management made easy