conventional-changelog
rust-cross
conventional-changelog | rust-cross | |
---|---|---|
12 | 5 | |
7,574 | 2,475 | |
0.8% | - | |
9.0 | 0.0 | |
9 days ago | almost 2 years ago | |
TypeScript | Shell | |
ISC License | Apache License 2.0 |
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.
conventional-changelog
-
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 ๐ฆ๐
-
Using semantic-release to automate releases and changelogs
conventional-changelog-conventionalcommits is a package used for creating conventional commits and has a bit more configuration possibilities with changelogs in contrast to the default Angular commit scheme.
-
Conventional Commits - Specification for Your Commit Messages
Finally, it is also interesting to be able to automatically generate the CHANGELOG file from the commit messages. There are various tools for this, one of them is Conventional Changelog
-
Minor imperfections that shout โbeginner codeโ
Some projects generate change logs automatically from commits. For example, angular uses conventional-changelog.
- GitHub Actions can't find built binaries to put them to a release
- FRONT END - LINKS CRIATIVOS E TรCNICOS
-
Confused about how to get my packages up to `1.0.0` using Lerna / Conventional commits...
I'm under the understanding from this issue that in semver, a package that is <1.0.0 is considered unstable. This means that a breaking change can occur at any version, usually between minors.
-
Automatically update git major tags on GitHub marketplace release
conventional-changelog-conventionalcommits
-
Keep a Changelog
[1] - https://github.com/conventional-changelog/conventional-chang...
-
What are some good practices for writing changelogs/update notes?
I dont use myself, but some people follows something like the conventional commit spec, and then uses a generator.
rust-cross
-
Anything C can do Rust can do Better
rust-cross, Everything you need to know about cross compiling Rust programs! - Jorge Aparicio
-
GitHub Actions can't find built binaries to put them to a release
on: push: tags: - 'v*' name: Cross-compile and release jobs: build: name: Build runs-on: ubuntu-latest strategy: matrix: target: # https://github.com/japaric/rust-cross#the-target-triple - x86_64-unknown-linux-gnu - x86_64-pc-windows-gnu - wasm32-unknown-emscripten steps: - uses: actions/checkout@v2 - uses: actions-rs/toolchain@v1 with: toolchain: stable target: ${{ matrix.target }} override: true - uses: actions-rs/cargo@v1 with: use-cross: true command: build args: --release --target=${{ matrix.target }} release: name: Release needs: [ build ] runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 with: clean: false - uses: nowsprinting/check-version-format-action@v3 id: version with: prefix: 'v' - name: Create release id: new_release uses: actions/create-release@v1 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} with: tag_name: ${{ github.ref }} release_name: Release ${{ github.ref }} body: | Changes in this release: - First change - Second change draft: false prerelease: false - name: Upload 64-bit Windows build uses: actions/upload-release-asset@v1 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} with: asset_path: target/release/client.exe asset_name: client-${{ matrix.target }}-${{ steps.version.outputs.full }}.exe asset_content_type: application/zip upload_url: ${{ steps.new_release.outputs.upload_url }} - name: Upload 64-bit Linux build uses: actions/upload-release-asset@v1 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} with: asset_path: target/release/client asset_name: client-${{ matrix.target }}-${{ steps.version.outputs.full }} asset_content_type: application/zip upload_url: ${{ steps.new_release.outputs.upload_url }} - name: Upload 32-bit WebAssembly build uses: actions/upload-release-asset@v1 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} with: asset_path: target/release/client.wasm asset_name: client-${{ matrix.target }}-${{ steps.version.outputs.full }}.wasm asset_content_type: application/zip upload_url: ${{ steps.new_release.outputs.upload_url }}
-
In support of single binary executable packages
Well, at least that's that easy if what you try to compile don't have C dependencies. For C dependencies, there is cross <https://github.com/japaric/rust-cross> which I had good experiences with.
-
Hey Rustaceans! Got an easy question? Ask here (15/2021)!
Oh, this was the first thing that came up: https://github.com/japaric/rust-cross
What are some alternatives?
keep-a-changelog - If you build software, keep a changelog.
xargo - The sysroot manager that lets you build and customize `std`
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
git-cliff - A highly customizable Changelog Generator that follows Conventional Commit specifications โฐ๏ธ
Module Linker - browse modules by clicking directly on "import" statements on GitHub
Release It! ๐ - ๐ Automate versioning and package publishing
just - ๐ค Just a command runner
release-please - generate release PRs based on the conventionalcommits.org spec
cargo-linked - Display linked packages for compiled rust binaries
rn-boilerplate - React native boilerplate with formik, ui kittens, eslint setup, and expo
iced - A cross-platform GUI library for Rust, inspired by Elm