semver
changesets
Our great sponsors
semver | changesets | |
---|---|---|
720 | 30 | |
7,020 | 7,998 | |
1.3% | 4.0% | |
2.3 | 5.7 | |
3 months ago | 6 days 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.
semver
-
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/
-
Semver 2.0.0 Released
Semver has been 2.0.0 for 10 years, look at the date of the assets. Multiple releases created today where none existed before. Not sure why someone is creating releases now, perhaps just some housekeeping/cleanup.
https://github.com/semver/semver/releases
-
First purchase advice
All ELRS hardware will talk to all other ELRS hardware, including Radiomaster's ELRS transmitters and receivers. There are one or two exceptions from scummy companies that have been pilloried by the community, and you probably won't find them anymore. So long as the ELRS firmware running on both devices has the same major version number, you're good to go. ie. 3.3.1 will still talk to 3.0.1, but won't talk to 2.0.0. (The "major version" is the 1st number, the "minor version" is the 2nd number, and the "patch version" is the 3rd number. See Semantic Versioning for more info.)
-
fkYAML v0.3.0: Support non-string-scalar nodes as mapping keys
If you're using semver, read the spec it's not overly long or hard to understand.
-
Immich will have breaking changes (again) in the next release
Semantic versioning actually has a clear rule about this:
changesets
-
I made a set of devtools for small projects
In my circles, this is the go-to for release automation / changelogs: https://github.com/changesets/changesets
-
Criando um Design System reutilizável entre React e React Native com Tamagui
🦋 Publicando com changesets
- Changesets
-
Nx - Highlights of 2023
Open source libraries and frameworks share a common necessity: the need to develop multiple packages cohesively and efficiently while managing their versioning and publishing to NPM. Nx has emerged as a go-to choice for handling such open source monorepos (as we'll explore further in the next section of this blog post). Until recently, one area Nx did not address directly was versioning and release management. Traditionally, this gap has been filled with tools like release-it, changesets, or custom Node scripts, similar to our approach in the Nx repository.
-
Automate NPM releases on GitHub using changesets 🦋
Doing these tasks by hand can quickly become a hassle. If you're open to receiving contributions from others, it can be an even bigger headache. In this post we'll cover how to use changesets to automate all of these steps.
- Show HN: Changesets, manage your versioning and changelogs
-
[AskJS] Advice on how to manage breaking changes in the first versions of a UI Library
For versioning we use changeset, but with fixed-packages. We have found that the user thinks updating and managing our dependencies much easier if they can just bump each package to the same version. (storybook, sanity follows this appoach). While it feels unintuitive that each package gets a major if just the CSS has breaking changes, the user don't really care. They just want to finish the chore of updating their dependencies fast, without having to understand the system that deeply. This also makes documenting the changes much easier!
- [Reactjs] React UI Composant Library Playplate
-
Hey guys, I made a small CLI to automatically update monorepo packages and NPM releases. I would like some feedback.
Thanks for sharing this. Why should I choose that instead of Changesets that work like a charm?
-
Conventional Commits - Am I missing something?
You’re right this information would be better suited for for commit trailers. A lot more information can be put there as well. For the purpose of changelog generation, what it’s commonly used for, it could just as well be put in the trailers and not crammed into the subject. I personally prefer changesets though.
What are some alternatives?
react-native - A framework for building native applications using React
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
semantic-release - :package::rocket: Fully automated version management and package publishing
nx - Smart Monorepos · Fast CI
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
Visual Studio Code - Visual Studio Code
helmfile - Deploy Kubernetes Helm Charts
pnpm - Fast, disk space efficient package manager
Poetry - Python packaging and dependency management made easy
berry - 📦🐈 Active development trunk for Yarn ⚒
TermuxBlack - Termux repository for hacking tools and packages
tsdx - Zero-config CLI for TypeScript package development