cargo-release
dprint
cargo-release | dprint | |
---|---|---|
11 | 21 | |
1,245 | 2,950 | |
1.2% | 1.6% | |
9.1 | 8.5 | |
1 day ago | 12 days ago | |
Rust | Rust | |
Apache 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.
cargo-release
-
Changelog-Driven Releases
My problem with maintaining a changelog during development is it can serve as a source of merge conflicts. Instead, I follow Covnentional Commit style and manually write my changelog entries based on the commits. I have a tool [0] that can show me the relevant commits for a package in my repo and automates the entire release process, including doing sanity checks.
I also feel like releasing from CI is hard, especially if you have multiple packages in a repo [1], including
- You can't as easily introspect the process
- You can't as easily recover from failure
- Getting a lot of the nuance right, like handling releases concurrent to merging of PRs, is difficult
- When the workflow is an ever-present "release PR" that you merge when ready has issues with selecting which packages to release and at what version
I have been considering making a tool to generate changelogs from fragments. Been keeping notes at https://github.com/epage/epage.github.io/issues/23
[0]: https://github.com/crate-ci/cargo-release
[1]: https://github.com/MarcoIeni/release-plz/discussions/1019
-
Oxlint – written in Rust – 50-100 Times Faster than ESLint
You should combine step 1 and 2 with CI. Just tag a version in your git, push to remote and have CI auto build a release for you.
Use github actions or other setup for other backends.
Or go nuts with cargo-release.
https://github.com/crate-ci/cargo-release
https://github.com/cargo-bins/release-pr
-
Rust 2030 Christmas list: Subcrate dependencies
tools like cargo-release
-
`toml` vs `toml_edit` (ie `toml` 0.6 is out)
Just to check, are you aware of cargo-edit's cargo-set-version or cargo-release?
-
What's everyone working on this week (45/2022)?
I released my first crate that provides a derive macro to easily obtain a name of a current variant in an enum as a string. I did it mostly to learn about procedural macros and the process of releasing a crate. I then found out there is strum which does this and much more. Nonetheless, I learned a lot and I found couple of nice tools like ```cargo-release and git-cliff.
- cargo-release v0.22 is out!
-
A GitHub Action for creating "Release PRs" for Cargo projects.
I'll note there is an issue in the cargo-release repo where this kind of workflow is wanted. https://github.com/crate-ci/cargo-release/issues/119
-
[Gitoxide December Update]: a new object database and upcoming multi-pack index support
cargo-release is on about the same level of features used
-
cargo-release v0.19
cargo-release automates the release process for your crate. For example, with clap, all I do is add entries to the CHANGELOG and run cargo release patch and cargo-release takes care of updating files, publishing to crates.io, tagging, and pushing.
-
Introducing `cargo smart-release` - the new way to release workspace crates
Yes, developers from all three tools were sharing ideas with each other recently
dprint
-
My opinion about opinionated Prettier: 👎
Currently, I am using ESLint for formatting of basic things like spacing and quotes. However, those rules were deprecated with v8.53.0 and moved to @stylistic/eslint-plugin. But they recommend Prettier or dprint.
- Oxlint – written in Rust – 50-100 Times Faster than ESLint
-
How do I stop Prettier from de-structuring object properties onto separate lines?
Prettier is opinionated. dprint is highly configurable.
-
Rome v12.1: a Rust-based linter formatter for TypeScript, JSX and JSON
I mean, I know I am a bad person because of those long names, but that is how life goes sometimes! And the blank line there at the top is just very important to like, catch one's breath, while reading this code.
(I'm really just posting this in the hopes that somebody will throw me a "Bro, just use hpstrlnt, it totally lets you configure that!" -- I have not actually tried Rome to see if it does (it's Monday morning and I'm not quite ready to be disappointed again...))
[1]: dprint is good, and I recommend it as the best code formatter I currently know of: https://dprint.dev/
- Is there an extension for forcing a code style?
- What would you rewrite in Rust?
-
What's the best way to generate code?
If it's something in the vein of one of those things then, worst case, you generate the code first, then run it through something like dprint.
- Ask HN: Alternatives to Prettier?
- dprint – Code Formatter
-
Announcing Rome Formatter
Why not compare Rome formatter to the actual competition, https://dprint.dev/ ?
What are some alternatives?
Rustup - The Rust toolchain installer
prettier - Prettier is an opinionated code formatter.
just - 🤖 Just a command runner
nvim-lspconfig - Quickstart configs for Nvim LSP
cargo-make - Rust task runner and build tool.
dotfiles - 👨🏻💻 My dotfiles including Neovim Lua config, ZSH with zinit plugin manager & powerlevel10k prompt
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
deno - A modern runtime for JavaScript and TypeScript.
cargo-ebuild - cargo extension that can generate ebuilds using the in-tree eclasses
apriori-rs - Apriori for association rule mining with Python bindings 🦀🐍
cargo-modules - Visualize/analyze a Rust crate's internal structure
deno_lint - Blazing fast linter for JavaScript and TypeScript written in Rust