terrathon
semantic-release
| terrathon | semantic-release | |
|---|---|---|
| 1 | 83 | |
| 1 | 20,536 | |
| - | 1.3% | |
| 0.0 | 9.3 | |
| over 2 years ago | 4 days ago | |
| Python | JavaScript | |
| Mozilla Public License 2.0 | 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.
terrathon
-
Meet Semverbot, a semver versioning CLI tool written in GoLang
https://github.com/restechnica/terrathon (python pip package)
semantic-release
-
Semantic versioning of NestJS and Angular applications in the NX monorepository
Unlike https://github.com/semantic-release/semantic-release , plugin https://github.com/TheUnderScorer/nx-semantic-release pre-starts building a dependency graph between libraries and applications, and then starts the release process for all related code.
-
Create and publish an npm library, with TypeScript and Semantic Versioning
semantic-release: Fully automatic; you can integrate it into GitHub CI to automatically update the version code and publish to npm each time you update your code on GitHub.
- Semantic-Release: Automate Versioning and Package Publishing with Ease
- Semantic-Release: Automate Versioning and Publishing with Zero Manual Steps
- Semantic-release – automated version management and package publishing
-
Git-cliff – Generate changelog from the Git history
I'm also pretty unclear on what the "bump" command does. Does this create a git tag? Make a new commit? Have hooks to update version constants in the source? Seems liek the answer to all of these is "no", and so I'm not really sure how useful it is.
I'm also aware of related tool in this space: semantic-release <https://github.com/semantic-release/semantic-release>. I haven't used it in my repositories, but it seems like a more comprehensive verison of git-cliff.
-
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 📦🚀
-
💡Automatic Deployment of your project dependencies updates on GCP : Efficiency vs. Cost?
Auto-tagging a project, Renovate or Dependabot can do this. With a Git Workflow and another tool like semantic-release you can do this. This behavior is a “gymnastic” to do on the CI/CD of your project but it’s not complicated. For example with GitLab CI, you can verify the pipeline run on the default branch of your project :
- alacritty-themes not working any more!!!
- Announcing @ngneat/avvvatars
What are some alternatives?
svu - Semantic Version Util
GitVersion - From git log to SemVer in no time
semverbot - A CLI which automates semver versioning.
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
cliwrap-python - A lightweight wrapper around CLIs for error handling and logging.
Release It! 🚀 - 🚀 Automate versioning and package publishing
homebrew-tap - Homebrew tap for Restechnica
release-drafter - Drafts your next release notes as pull requests are merged into master.
git-chglog - CHANGELOG generator implemented in Go (Golang).
commitlint - 📓 Lint commit messages
gradle-git-versioner - A Gradle plugin to automatically version a project based on commit messages and semantic versioning principles
semver - Semantic Versioning Specification