Release It! π
semantic-release
Our great sponsors
Release It! π | semantic-release | |
---|---|---|
9 | 75 | |
7,454 | 19,610 | |
2.0% | 1.5% | |
8.3 | 9.4 | |
15 days ago | 5 days ago | |
JavaScript | JavaScript | |
MIT License | 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.
Release It! π
-
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.
-
How does the typescript-eslint project generate its changelogs?
Hi. I'm maintaining a small monorepo and I'd like to learn techniques from large, mature projects like typescript-eslint. I assume they automate changelogs from commit logs and/or PRs, but I can't figure out how they do it by looking at their source code. I do know of tools like release-it that helps automate the process; do the typescript-eslint maintainers use such a tool, or use a homegrown one?
-
Quickly start developing your own npm package library with NestJS.
This is a quick start guide for setting up a NestJS project for creating your own package library with automated versioning and package publishing. https://github.com/Emgevorgyan/nestjs-package-quick-start
-
Package Publishing Reading & Resources
Release It! - This seems promising. A CLI tool that can be used in interactive or continuous integration mode. The big appeal for me is a Yarn workspaces specific plugin.
-
Monorepo is so frustrating...
Fine, but I need a package release tool and release-it tools looks good. I install, configure and on the last step - publishing - I find out that this lib does not support monorepo... https://github.com/release-it/release-it/issues/831 and the release-it-yarn-workspaces lib does not support the latest version of release-it https://github.com/rwjblue/release-it-yarn-workspaces/issues/68
-
My ideal Rust workflow
May be less relevant for your particular workflow (because npm-specific and because everything is internal for you), but Iβm a big fan of an alternative in the auto-release-generation space: the combo of release-it and release-it-lerna-changelog, which give you the same kind of automation but donβt require specific git commit messages, because instead the combo uses the GH API and labels to generate the changelog. This is a muuuuuch nicer experience for external contributors, because it puts the responsibility for that back on maintainers instead.
-
DynamoDB GUI with Electron, React & Typescript
Release It - To create tags, bump the versions, manage release betas and detect merged changes.
-
Writing a High Quality README! π₯
Release It
semantic-release
- alacritty-themes not working any more!!!
- Announcing @ngneat/avvvatars
- Auto versioning?
-
How to set up Commitzen with Husky
Conventional commits specification contains a set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of, for example, semantic release. You can manually follow this convention in your project or use a tool to assist you, such as Commitizen.
-
Automated release with Semantic Release and commitizen
When working with JavaScript projects, managing version numbers and commit messages is important for the maintainability of the project. Since 2020 I have been the main developer of Atomic Calendar Revive a highly customisable Home Assistant calendar card, I found maintaining versions and releases to be cumbersome until recently. In this article, I will introduce the commitizen and semantic-release packages for creation or appropriate commit messages and semantic versioning. I will also provide examples of how I am currently using these packages to streamline my release workflow and project maintenance.
- π¦ Effortless Data Quality w/duckdb on GitHub βΎοΈ
-
How I Sliced Deployment Times to a Fraction and Achieved Lightning-Fast Deployments with GitHub Actions
To further streamline deployments, I introduced semantic-release. This tool automates commit tagging and tracks changes since the previous version. As a result, deployments now occur only when new tags are present, saving us valuable minutes.
-
What are some examples of good release notes from open source projects that you have come across?
If your projects ar made in javascript and related tools, I'd suggest you to check: semantic-release
- π Mobile App deployment automation π±
- GitOps/Argo CD Deployment Flow Question
What are some alternatives?
GitVersion - From git log to SemVer in no time
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
release-drafter - Drafts your next release notes as pull requests are merged into master.
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
cz-cli - The commitizen command line utility. #BlackLivesMatter
tsdx - Zero-config CLI for TypeScript package development
keel - Kubernetes Operator to automate Helm, DaemonSet, StatefulSet & Deployment updates
autochecker - β»οΈ Test your libraries in many different versions of NodeJS, Ruby, Java and many other languages
action-semantic-pull-request - A GitHub Action that ensures that your PR title matches the Conventional Commits spec.
gitlab