setup-bun
mc-publish
setup-bun | mc-publish | |
---|---|---|
1 | 1 | |
342 | 200 | |
8.8% | - | |
6.9 | 9.1 | |
28 days ago | 13 days ago | |
TypeScript | TypeScript | |
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.
setup-bun
-
Yarn 4.0
I use Bun in CI too, and they have a clean GitHub Action for it: https://github.com/oven-sh/setup-bun.
Actually now that you mention CI, I remember now that I did also run into non-deterministic problems runnign type checks on projects with Bun using Github's free runner.
Errors looked like this, but it worked fine every 2/3 runs with the exact same code:
mc-publish
-
Curseforge Revenue and History
I personally use mc-publish, all I need to do is push a version to GitHub releases and it automatically uploads that to CurseForge and Modrinth.
What are some alternatives?
issue-action - github action for github issue
add-and-commit - :octocat: Automatically commit changes made in your workflow run directly to your repo
pn - This is an experimental wrapper over the pnpm CLI written in Rust
anglerci - A validation-only approach to releasing projects using NPM and Git.
pnpm.io - pnpm's website
FTP-Deploy-Action - Deploys a GitHub project to a FTP server using GitHub actions
setup-graalvm - GitHub Action for setting up GraalVM distributions.
changed-files - :octocat: Github action to retrieve all (added, copied, modified, deleted, renamed, type changed, unmerged, unknown) files and directories.
pyenv-action - Enables pyenv within your github actions workflow
pr-compliance-action - Check PR for compliance on title, linked issues, and files changed