semantic-release
execa
Our great sponsors
semantic-release | execa | |
---|---|---|
75 | 20 | |
19,768 | 6,334 | |
1.6% | - | |
9.4 | 9.5 | |
4 days ago | 6 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.
semantic-release
- alacritty-themes not working any more!!!
- Announcing @ngneat/avvvatars
- Auto versioning?
-
Is it possible to bypass merge queue requirement for a GitHub app without needing admin permissions?
I'm trying to improve the security behind our release process, which uses semantic-release. During this process, it creates a change log which is committed to the repo, publishes a package and a few other things.
-
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.
- Automated Release Notes in Azure Devops
-
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
execa
-
Google ZX โ A tool for writing better scripts
Iโm partial to Sindre Sorhusโ execa, this document outlines the differences:
https://github.com/sindresorhus/execa/blob/main/docs/scripts...
- Execa: Process Execution for Humans in Node.js
-
The Bun Shell
Yeah, or over https://github.com/sindresorhus/execa?
And given the existence of those npm packages, is there any aspect of Bun Shell that required it to be built into the Bun runtime instead of published to npm?
For something which works across all JS runtimes (Deno, Node) and achieves basically the same, check out the popular JS library Execa[1]. Works like a charm!
[1]: https://github.com/sindresorhus/execa
-
Building Reactive CLIs with Ink - React CLI library
To simplify the process of running the commands, I will use execa - abstraction library on top of Node.js child_process methods.
-
How to run DB migrations in CICD Pipeline
Hello, this is an interesting problem. At https://stacktape.com (where we're creating a developer-friendly abstraction of AWS), we're recommending 2 options: - use a "deployment script" (basically a custom-resource lambda function that runs during the CloudFormation deployment). You can install prisma into it, and then execute the migration command from the lambda function using something like execa, if you're using Javascript/Typescript. You can easily do this with Stacktape anytime. - use a bastion (EC2) instance (deployed to the the VPC where your RDS db is). The cheapest instances cost ~4.5$/month, so it shoudln't be too costly. You can also securely connect to it using EC2 instance connect, that leverages IAM to grant permissions to connect to it. (this is something we're currently implementing as Stacktape, and will be ready in ~2 weeks).
- Fluent shell scripts with JavaScript
-
Testing in ReScript
For FE, itโs usually Cypress or Playwright; for BE, itโs to run a server and start sending requests; for CLI, I like the tool called execa.
-
How to use execa@6 with NestJs?
Since version 6 execa is pure ES module. An attempt to import a package into NestJS project results in an error:
-
Getting vim ex command output without a TTY?
Essentially when I run this from my shell I get a listing of keymaps configured for vim. However, when I run it from a program without a PTY or TTY (e.g., via Rust's Command or Node's execa) I get an exit code of 0 and no output.
What are some alternatives?
GitVersion - From git log to SemVer in no time
zx - A tool for writing better scripts
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
Release It! ๐ - ๐ Automate versioning and package publishing
nodegit - Native Node bindings to Git.
release-drafter - Drafts your next release notes as pull requests are merged into master.
schemapack - Create a schema object to encode/decode your JSON in to a compact byte buffer with no overhead.
commitlint - ๐ Lint commit messages
hypernova - A service for server-side rendering your JavaScript views
gradle-git-versioner - A Gradle plugin to automatically version a project based on commit messages and semantic versioning principles
nan - Native Abstractions for Node.js