Merge branch 'cargo-target'

Author: Byron

CHANGELOG.md

@@ -5,6 +5,13 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## Unreleased
+
+### Features
+
+ - Allow specifying a `--target` triple when running `cargo smart-release`, forwarding it to `cargo publish` so crates that don't
+   compile for the host can still be released ([#89](https://github.com/GitoxideLabs/cargo-smart-release/issues/89)).
+
 ## 0.21.8 (2025-08-03)
 
 ### Bug Fixes
@@ -2776,4 +2783,3 @@ For more information, run `cargo changelog -h`.
 ## v0.1.0 (2021-08-13)
 
 - initial release
-

README.md

@@ -7,27 +7,29 @@ Fearlessly release workspace crates and with beautiful semi-handcrafted changelo
 ## Key Features
 
 * **zero-configuration**
-  * `cargo smart-release` needs no extra flags to _do the right thing™️_ smartly. If your intervention is needed it will let you know before it makes changes.
-  * It won't do anything if there are no changes.
+    * `cargo smart-release` needs no extra flags to _do the right thing™️_ smartly. If your intervention is needed it will let you know before it makes changes.
+    * It won't do anything if there are no changes.
 * **made for multi-crate workspaces**
-  * "Nothing stands by itself, and everything is interconnected" - is how it sees the world, allowing it to efficiently handling complex workspace graphs.
-  * _works just as well for single-crate workspaces_
+    * "Nothing stands by itself, and everything is interconnected" - is how it sees the world, allowing it to efficiently handling complex workspace graphs.
+    * _works just as well for single-crate workspaces_
 * **changelogs-deluxe**
-  * It maintains beautiful changelogs for you while allowing you to edit them for the final polish.
-  * See your release notes via in-repository _tag objects_ and in _GitHub Releases_
-  * **plays well with `cargo release`**
-    * `cargo changelog` writes changelogs non-destructively, and only that, leaving the release workflow to [cargo-release].
-  
+    * It maintains beautiful changelogs for you while allowing you to edit them for the final polish.
+    * See your release notes via in-repository _tag objects_ and in _GitHub Releases_
+    * **plays well with `cargo release`**
+        * `cargo changelog` writes changelogs non-destructively, and only that, leaving the release workflow to [cargo-release].
+
 If seeing is believing, here is [a 12 minute demonstration](https://www.youtube.com/watch?v=EOft_uMDVYE), and the same in 30 minutes is [also available](https://youtu.be/a4CzzxJ7ecE).
 
 ## Made for this Workflow
 
 When developing various crates in a workspace, when committing changes and if the edit is breaking, a feature, or another
 change I want to see in changelogs, [conventional] git messages will be used. This helps building changelog scaffolding automatically later.
 
-When ready for releasing a particular crate or set of crates of interest, run `cargo smart-release [<crate-name> ...]` to simulate a release. For particularly thorough
-but error-prone simulations (as in false positives) one could run `cargo smart-release --dry-run-cargo-publish`. To polish changelogs, run `cargo changelog --write <crate-name>`
-to update the scaffolding and edit it by hand until it fits.
+When ready for releasing a particular crate or set of crates of interest, run `cargo smart-release [<crate-name> ...]` to simulate a release.
+To polish changelogs, run `cargo changelog --write <crate-name>` to update the scaffolding and edit it by hand until it fits.
+
+For particularly thorough but error-prone simulations (as in false positives) one could run `cargo smart-release --dry-run-cargo-publish`.
+Crates that don't compile for the host can be released by passing `--target <triple>`, which is forwarded to every `cargo publish` invocation (including dry runs).
 
 After evaluating the release procedure and following instructions,
 `cargo smart-release --execute` will cause the fully automatic release of one or more crates.
@@ -39,6 +41,7 @@ There are various other options that shouldn't be needed in the common case, use
 ## Installation
 
 ### Cargo
+
 Via `cargo`, which can be obtained using [rustup][rustup]
 
 ```
@@ -87,7 +90,7 @@ Here is what `cargo smart-release` does differently: "It tries really hard to do
 
 ## Limitations
 
-* it requires tables to be used when specifying versions, i.e. `crate = { version = "1" }` instead of `crate  = "1".
+* it requires tables to be used when specifying versions, i.e. `crate = { version = "1" }` instead of `crate = "1".
 * it gracefully fails when encountering version requirement comparators which are not `^`, like `=`
 * it's tested only by using it on `gitoxide`, there are only very few regression tests with little coverage.
 * short object ids in changelogs may be ambiguous, as they are unconditionally truncated to 7 characters.
@@ -109,5 +112,7 @@ Thanks to [cargo-release] for showing the way and for incredible fast response t
 Special thanks go to [git-cliff] which gave me the nudge needed to want to write my own.
 
 [cargo-release]: https://github.com/sunng87/cargo-release/issues/224
+
 [git-cliff]: https://github.com/orhun/git-cliff
+
 [rustup]: https://rustup.rs/

src/cli/main.rs

@@ -64,6 +64,7 @@ fn main() -> anyhow::Result<()> {
             no_isolate_dependencies_from_breaking_changes,
             capitalize_commit,
             registry,
+            target,
             signoff,
             commit_prefix,
         } => {
@@ -95,6 +96,7 @@ fn main() -> anyhow::Result<()> {
                     allow_changelog_github_release: !no_changelog_github_release,
                     capitalize_commit,
                     registry,
+                    target,
                     signoff,
                     commit_prefix,
                 },

src/cli/options.rs

@@ -152,6 +152,12 @@ pub enum SubCommands {
         #[clap(long, help_heading = Some("CUSTOMIZATION"))]
         registry: Option<String>,
 
+        /// Build and package the crate for the given target triple when invoking `cargo publish`.
+        ///
+        /// This flag is forwarded to all `cargo publish` invocations, including dry runs.
+        #[clap(long, help_heading = Some("CUSTOMIZATION"))]
+        target: Option<String>,
+
         /// Pass --no-verify to 'cargo publish' which should only be a last resort when fixing up packages that
         /// otherwise wouldn't publish, but need to be publish to resolve the situation.
         #[clap(long, help_heading = Some("EXPERT"))]

src/command/mod.rs

@@ -28,6 +28,7 @@ pub mod release {
         pub allow_changelog_github_release: bool,
         pub capitalize_commit: bool,
         pub registry: Option<String>,
+        pub target: Option<String>,
         pub signoff: bool,
         pub commit_prefix: Option<String>,
     }

src/command/release/cargo.rs

@@ -17,6 +17,7 @@ pub(in crate::command::release_impl) fn publish_crate(
         no_verify,
         verbose,
         registry,
+        target,
         ..
     }: Options,
 ) -> anyhow::Result<()> {
@@ -33,6 +34,9 @@ pub(in crate::command::release_impl) fn publish_crate(
         if let Some(ref registry) = registry {
             c.arg("--registry").arg(registry);
         }
+        if let Some(ref target) = target {
+            c.arg("--target").arg(target);
+        }
 
         if allow_dirty {
             c.arg("--allow-dirty");