eget
semver
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.
eget
-
Essential Command Line Tools for Developers
View on GitHub
- gh-dl: download releases from github repo
-
Install GitHub release binaries from the CLI interactively
would be good if you added a comparison with https://github.com/zyedidia/eget on your repo
-
The culmination of several months of work by dozens of people, Flatpak 1.14.0 is now out!
There used to be a project called ginstall.sh that kept like, a manually maintained database of various projects with static binaries and how to install them. It still exists, but maintenance stopped because its model was also not sustainable. Its use case is better covered by tools like asdf, stew, and if you want to get even simpler, eget.
- An ode to Flatpak (and Fedora Silverblue)
-
Asdf Performance
I'm a huge fan of asdf and have been using for years together with direnv! It's great to see how much effort is put into it! I hope more people adopt it so that we don't have to `curl | sh`! One thing I have issues with asdf is security as are no checksums, so, you if I project get compromised you'll get compromised, too. This, of course, is in addition to the third-party asdf plugin getting itself compromised (which is the greater risk). Last, but not least - I wish asdf came with something like eget [0] incorporated so that it can install 99% of the plugins directly and safely! Last, but not least - 99% of the plugins have almost identical code and all that changes is the repo, so, this should be generalized. For example, many years ago I made just one codebase of all HashiCorp plugins [1] and it's been working great!
[0]: https://github.com/zyedidia/eget
[1]: https://github.com/asdf-community/asdf-hashicorp
- get latest github
- Eget – Easily install prebuilt binaries from GitHub
- Zyedidia/eget: Easily install prebuilt binaries from GitHub
- Eget - Easily install prebuilt binaries from GitHub
semver
-
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/
-
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
What are some alternatives?
fetch - Download files, folders, and release assets from a specific git commit, branch, or tag of public and private GitHub repos.
react-native - A framework for building native applications using React
stew - 🥘 An independent package manager for compiled binaries.
semantic-release - :package::rocket: Fully automated version management and package publishing
bin - Effortless binary manager
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
pastel - A command-line tool to generate, analyze, convert and manipulate colors
changesets - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
flatpak-external-data-checker - A tool for checking if the external data used in Flatpak manifests is still up to date
helmfile - Deploy Kubernetes Helm Charts
office365-pol - [OUTDATED] A PlayOnLinux script that utilizes the version of Wine made for CrossOver to run Microsoft 365 Apps / Office 365 without requiring any paid CrossOver components
Poetry - Python packaging and dependency management made easy