semantic-release-toolkit
semver
semantic-release-toolkit | semver | |
---|---|---|
1 | 728 | |
11 | 7,067 | |
- | 0.6% | |
2.4 | 0.6 | |
15 days ago | about 2 months ago | |
TypeScript | ||
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.
semantic-release-toolkit
-
You donβt need semantic-release (sometimes)
Iβm a big fan of semantic-release since it appeared. I followed its development, studied its inners. I did in-house reports, held workshops and finally brought semrel to our build infrastructure. I wrote plugins, plugin-factories and testing-tools for it. For several years now, I've been trying to combine semantic releases and monorepositories in many OSS projects:
semver
-
Python wheel filenames have no canonical form
The odd vs even versions rule you describe, while followed by a few projects, is not part of Semantic Versioning (aka SemVer). No mention of it whatsoever in the spec at https://semver.org/. Pre-release versions under SemVer are indicated by a hyphenated suffix after the patch version - e.g. 1.2.3-alpha
-
How I Build Paradise UI: A React UI Component Library
Paradise UI follow Semantic Versioning convention. Semantic versioning is a widely-adopted version scheme that encodes a version by a three-part version number (Major.Minor.Patch), for example version 1.1.1.
-
The ultimate guide to creating a secure Python package
As specified earlier in the tutorial, you can version your Python package by using a version number and including it in the package's documentation. The version number should follow the commonly used semantic versioning format MAJOR.MINOR.PATCH, where MAJOR represents significant changes in the project, MINOR represents new features, and PATCH represents bug fixes or performance improvements.
-
The right development flow: Better than Agile
We increase the version of our product as specified in SemVer and deploy it to production, preferably following good deployment practices to have no downtime.
-
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
What are some alternatives?
multi-semantic-release - Proof of concept that wraps semantic-release to work with monorepos.
react-native - A framework for building native applications using React
npm - :ship: semantic-release plugin to publish a npm package
semantic-release - :package::rocket: Fully automated version management and package publishing
multi-semantic-release - Proof of concept that wraps semantic-release to work with monorepos.
changesets - π¦ A way to manage your versioning and changelogs with a focus on monorepos
zx-semrel - `zx`-based release script as `semantic-release` alternative (PoC)
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
semantic-release-monorepo-hooks - Workarounds to handle `semantic-release-monorepo` multipublishing
helmfile - Deploy Kubernetes Helm Charts
exec - :shell: semantic-release plugin to execute custom shell commands
Poetry - Python packaging and dependency management made easy