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.
felesatra
-
Some Notes on Upgrading Hugo
> I could have just built my own SSG
That's actually what I did when I tried using Hugo. Go is very well suited for it.
https://github.com/darkfeline/felesatra/blob/master/kanade/c...
semver
-
Helm Chart Essentials & Writing Effective Charts 🚀
Update version in Chart.yaml according to SemVer principles.
-
How to Publish Your First npm Package: A Step-by-Step Guide
version: The version number, following semantic versioning.
-
All the Git Commands You Need to Know
You can then add a commit message to your check-in. Some developer teams follow the Conventional Commit specification when adding commit messages, which dovetails SemVer and makes it easier to publish release notes based on widely known standards.
-
Starting with semver `1.0.0`
But after reading this interesting Issue on the semver repo: https://github.com/semver/semver/issues/221 my opinion is changing. Using version 0.x indicates instability, true, but the reality is that some libraries are unstable.
- Seu Primeiro Pacote NuGet: Um Passo a Passo Prático
-
Htmx 2.0.4 Released
In addition to what the siblings say, in case parent isn't aware of semantic versioning: https://semver.org/
-
# How to write good commit messages
Senamtic Versioning - https://semver.org/
-
Dependency management fatigue, or why I forever ditched React for Go+Htmx+Templ
It seems to me that a lot of people are forgetting that when updating to next major version of a package, breaking changes are expected - that's the whole point of major version number in SemVer [1]. What they actually want is seamless updates (or never changing APIs, but that not possible in most situations, and also not what you want as a package developer - you want to be able to correct your API design mistakes). That requires a lot of work from the package developers.
Look for example how people at Remix do it: breaking changes are hidden behind future flags [2], so you a user can turn them on one by one and adapt their code on gradually without surprises. Another solution is creating codemods for upgrades. But how many open-source package developers are willing do to this extra work?
Same story with peer dependencies - they're completely fine, if package developers know how to use them.
As always, don't be mad at React, don't curse Npm, it's not their fault. There is no great package without great effort.
[1] https://semver.org/
- Semantic Versioning using GitVersion YAML file for your .NET, Java, and Kotlin projects' CI/CD
-
Semantic Versioning: A Universal Language for Software Updates
You can always check the official Semantic Versioning Specification.
What are some alternatives?
gutenberg - A fast static site generator in a single binary with everything built-in. https://www.getzola.org
semantic-release - :package::rocket: Fully automated version management and package publishing
react-native - A framework for building native applications using React
changesets - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
TermuxBlack - Termux repository for hacking tools and packages
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
helmfile - Deploy Kubernetes Helm Charts
cs-topics - My personal curriculum covering basic CS topics. This might be useful for self-taught developers... A work in development! This might take a very long time to get finished!
fswatch - A cross-platform file change monitor with multiple backends: Apple OS X File System Events, *BSD kqueue, Solaris/Illumos File Events Notification, Linux inotify, Microsoft Windows and a stat()-based backend.
Poetry - Python packaging and dependency management made easy
keep-a-changelog - If you build software, keep a changelog.
gitflow - Git extensions to provide high-level repository operations for Vincent Driessen's branching model.