semver
gitflow
Our great sponsors
semver | gitflow | |
---|---|---|
720 | 133 | |
7,020 | 26,516 | |
1.3% | - | |
2.3 | 0.0 | |
3 months ago | about 2 months ago | |
Shell | ||
- | GNU General Public License v3.0 or later |
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:
gitflow
-
FeiFlow - An Opinioned Git Branching And Release Management Strategy
1. GitFlow
-
Git Branches as a Social Construct
Pull Requests (or Merge Requests) are merged only when (1) all of the automated tests pass; and (2) enough necessary reviewers have indicated approval.
Git doesn't tell you when it's necessary to have full test coverage and manual infosec review in development cycles that produce releases, and neither do Pull Requests.
https://westurner.github.io/hnlog/#comment-19552164 ctrl-f hubflow
It looks like datasift's gitflow/hubflow docs are 404'ing, but the original nvie blog post [1] has the Git branching workflow diagrams; which the wpsharks/hubflow fork [3] of datasift/gitflow fork [2] of gitflow [1]has a copy of in the README:
[1] https://github.com/nvie/gitflow
[2] https://github.com/datasift/gitflow
[3] https://github.com/wpsharks/hubflow?tab=readme-ov-file
https://learngitbranching.js.org/ is still a great resource, and it could work on mobile devices.
The math of VCS deltas and mutable and immutable content-addressed DAG nodes identified by 2^n bits describing repo/$((2*inf)) bits ;
>> "ugit – Learn Git Internals by Building Git in Python" https://www.leshenko.net/p/ugit/
SLSA.dev is a social construct atop e.g. git, which is really a low-level purpose-built tool and Perl and now Python porcelain.
jj (jujutsu) is a git-compatible VCS CLI: https://github.com/martinvonz/jj
"Ask HN: Best Git workflow for small teams" (2016)
-
"Мобильная" разработка. [Системы контроля версий, Git]
A successful Git branching model - известная модель ветвления от Vincent Driessen.
- A successful Git branching model (2010)
-
Moving Fast: A Retrospective on Trunk-based Development
Before embarking on the project, we needed to decide on our Git workflow. Having experienced the unnecessary indirection and bureaucracy of Gitflow, I immediately proposed and implemented a trunk-based strategy instead.
-
Setting up GitHub Actions to deploy your website via FTP
As a best practice, consider creating a dev branch where you can stage your code and collaborate with other developers on your team. Alternatively, you can follow the Trunk-based development branching strategy. For larger teams and complex deployment cycles, the Gitflow branching model might be more suitable.
- Gitflow and GitHub Flow Compared
-
How do you use Git?
Note - this IS NOT Git Flow, which is way too complicated for what we're doing. Even the person who created Git Flow has some warnings and thoughts about it, 10 years later (https://nvie.com/posts/a-successful-git-branching-model/).
-
What strategy are you using versioning firmware with hardware in a VCS?
just use Gitflow
-
Adding @since tag when you don't know
Git and this: https://nvie.com/posts/a-successful-git-branching-model/
What are some alternatives?
react-native - A framework for building native applications using React
argocd-example-apps - Example Apps to Demonstrate Argo CD
semantic-release - :package::rocket: Fully automated version management and package publishing
release-please - generate release PRs based on the conventionalcommits.org spec
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
laragon - Laragon is a portable, isolated, fast & powerful universal development environment for PHP, Node.js, Python, Java, Go, Ruby. It is fast, lightweight, easy-to-use and easy-to-extend.
changesets - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
git-plan - Git Plan - a better workflow for git
helmfile - Deploy Kubernetes Helm Charts
GitVersion - From git log to SemVer in no time
Poetry - Python packaging and dependency management made easy
metacpan-web - Web interface for MetaCPAN