development/cargo
development/cargo
1
0
Fork 0
mirror of https://github.com/rust-lang/cargo synced 2024-07-17 11:08:08 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
16774 commits 76 branches 99 tags 84 MiB
Commit graph

715 commits

Author SHA1 Message Date
renovate[bot] ae0894d7df
chore(deps): update rust crate supports-hyperlinks to v3 2024-03-01 02:01:55 +00:00
Weihang Lo edd2821f46
chore: bump baseline version requirement of sub crates 
While we can just bump to the latest versions, this time we do a
conservative one for some crates.

* `cargo-util` --- 0.2.10 to 0.2.11 contain only comment changes.
* `cargo-platform` --- 0.1.6 to 0.1.8 contain only lint and metadata changes
 2024-02-26 18:38:49 -05:00
Ed Page b14a70fe09 test(cli): Verify terminal styling 
This uses a new feature from snapbox that let's us render terminal
styling in SVG files.  This let's us see / visualize ANSI escape codes,
including in github's UI (will render images, including side-by-side
images for diffs).
 2024-02-21 20:20:41 -06:00
bors 9090349adc Auto merge of #13441 - epage:snapbox, r=Muscraft 
chore: Update snapbox
 2024-02-16 16:56:57 +00:00
Ed Page 9f31f8c675 chore: Update snapbox 2024-02-16 10:27:48 -06:00
bors 8ad0e18b54 Auto merge of #13449 - Xeonacid:openssl, r=epage 
chore(deps): update openssl to 3.2.1 again

https://github.com/rust-lang/cargo/pull/13159 had updated to 3.2.0 and https://github.com/rust-lang/cargo/pull/13179 reverted to 1.1.1 for riscv64 build.

riscv64 build issue fixed and released in openssl-src 300.2.3+3.2.1: https://github.com/alexcrichton/openssl-src-rs/pull/230

Update to 3.2.1 from 3.2.0 should be safe.
 2024-02-16 14:51:43 +00:00
Xeonacid 37df88f0c9
chore(deps): update openssl to 3.2.1 again 
https://github.com/rust-lang/cargo/pull/13159 had updated to 3.2.0 and https://github.com/rust-lang/cargo/pull/13179 reverted to 1.1.1 for riscv64 build.

riscv64 build issue fixed and released in openssl-src 300.2.3+3.2.1: https://github.com/alexcrichton/openssl-src-rs/pull/230

Update to 3.2.1 from 3.2.0 should be safe.

Signed-off-by: Xeonacid <xeonacid@hit.edu.cn>
 2024-02-16 21:49:04 +08:00
Ed Page 6f93fa701e fix(test): Suggest -- for libtest arguments 
We already do this so long as the argument doesn't look like a
`cargo test` argument (e.g. `--show-output`)
but `--ignored` looks like `--ignore-rust-version` do the the suggestion
algorithms prefix checks.

Before
```
error: unexpected argument '--ignored' found

  tip: a similar argument exists: '--ignore-rust-version'

Usage: cargo test --ignore-rust-version [TESTNAME] [-- [ARGS]...]

For more information, try '--help'.
```
After
```
error: unexpected argument '--ignored' found

  tip: a similar argument exists: '--ignore-rust-version'
  tip: to pass '--ignored' as a value, use '-- --ignored'

Usage: cargo test --ignore-rust-version [TESTNAME] [-- [ARGS]...]

For more information, try '--help'.
```

Fixes #12494
 2024-02-16 07:11:12 -06:00
renovate[bot] 5ea658df78 chore(deps): update msrv (1 version) to v1.76.0 2024-02-08 14:32:51 +00:00
Weihang Lo 3dcb66b791
chore: update to jobserver 0.1.28 2024-02-08 08:32:07 -05:00
bors d7d48e4598 Auto merge of #13402 - epage:add, r=weihanglo 
fix: Don't duplicate comments when editing TOML

### What does this PR try to resolve?

`toml_edit` <0.22 has a bug that will cause
```toml
[lints]
rust.unsafe_op_in_unsafe_fn = "deny"

rust.explicit_outlives_requirements = "warn"
# rust.unused_crate_dependencies = "warn"

clippy.cast_lossless = "warn"
clippy.doc_markdown = "warn"
clippy.exhaustive_enums = "warn"
```
to be written out as
```toml
[lints]
rust.unsafe_op_in_unsafe_fn = "deny"
rust.explicit_outlives_requirements = "warn"
# rust.unused_crate_dependencies = "warn"

clippy.cast_lossless = "warn"
# rust.unused_crate_dependencies = "warn"

clippy.doc_markdown = "warn"
# rust.unused_crate_dependencies = "warn"

clippy.exhaustive_enums = "warn"
```
when it is parsed and then saved.

See toml-rs/toml#673

This affects any format-preserving edits we do, including:
- `cargo add`
- `cargo remove`
- `cargo init` / `cargo new` editing the workspace

### How should we test and review this PR?

I didn't add any tests as this is covered by `toml_edit`s tests (we already don't cover a fraction of the edit preserving tests it has)

### Additional information
 2024-02-07 16:23:04 +00:00
Eric Huss c30c13b3f1 Update git2 2024-02-06 20:11:27 -08:00
Ed Page 12cf56abf1 fix: Don't duplicate comments when editing TOML 
`toml_edit` <0.22 has a bug that will cause
```toml
[lints]
rust.unsafe_op_in_unsafe_fn = "deny"

rust.explicit_outlives_requirements = "warn"

clippy.cast_lossless = "warn"
clippy.doc_markdown = "warn"
clippy.exhaustive_enums = "warn"
```
to be written out as
[lints]
rust.unsafe_op_in_unsafe_fn = "deny"
rust.explicit_outlives_requirements = "warn"

clippy.cast_lossless = "warn"

clippy.doc_markdown = "warn"

clippy.exhaustive_enums = "warn"
```
when it is parsed and then saved.

See toml-rs/toml#675

This affects any format-preserving edits we do, including:
- `cargo add`
- `cargo remove`
- `cargo init` / `cargo new` editing the workspace
 2024-02-05 16:50:59 -06:00
Eric Huss 29ee35a9b3 Remove build metadata from curl-sys version. 2024-02-05 13:17:42 -08:00
bors fe60f0e561 Auto merge of #13380 - rust-lang:renovate/gix, r=epage 
chore(deps): update gix

[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [gix](https://togithub.com/Byron/gitoxide) | workspace.dependencies | minor | `0.57.1` -> `0.58.0` |
| [gix-features-for-configuration-only](https://togithub.com/Byron/gitoxide) | workspace.dependencies | minor | `0.37.1` -> `0.38.0` |

---

### Release Notes

<details>
<summary>Byron/gitoxide (gix)</summary>

### [`v0.58.0`](https://togithub.com/Byron/gitoxide/releases/tag/gix-v0.58.0): gix v0.58.0

[Compare Source](https://togithub.com/Byron/gitoxide/compare/gix-v0.57.1...gix-v0.58.0)

##### New Features

-   add `max-control` feature for fine-grained performance control.
    This also adds the following performance features:

    -   `zlib-ng`
-   `zlib-ng-compat`
-   `zlib-stock`
-   `parallel-walkdir`

##### Bug Fixes

-   `object::tree::diff::Platform::for_each_to_obtain_tree(callback)` errors are more convenient to use.
    Due to a change in how the generic error type is declared it should now be possible to
    use `anyhow` with it as well.

##### Commit Statistics

-   13 commits contributed to the release over the course of 18 calendar days.
-   20 days passed between releases.
-   4 commits were understood as [conventional](https://www.conventionalcommits.org).
-   1 unique issue was worked on: [#&#8203;670](https://togithub.com/Byron/gitoxide/issues/670)

##### Commit Details

<csr-read-only-do-not-edit/>

<details><summary>view details</summary>

-   **[#&#8203;670](https://togithub.com/Byron/gitoxide/issues/670)**
    -   `object::tree::diff::Platform::for_each_to_obtain_tree(callback)` errors are more convenient to use. ([`e3c5a0f`](https://togithub.com/Byron/gitoxide/commit/e3c5a0f))
-   **Uncategorized**
    -   Prepare changelogs prior to release ([`6a2e0be`](https://togithub.com/Byron/gitoxide/commit/6a2e0be))
    -   Merge branch 'finegrained-features' ([`d8570d0`](https://togithub.com/Byron/gitoxide/commit/d8570d0))
    -   Add `max-control` feature for fine-grained performance control. ([`8847676`](https://togithub.com/Byron/gitoxide/commit/8847676))
    -   Merge branch 'dirwalk' ([`5d176fc`](https://togithub.com/Byron/gitoxide/commit/5d176fc))
    -   Use `gix_fs::current_dir(precompose_unicode)`. ([`7d8d167`](https://togithub.com/Byron/gitoxide/commit/7d8d167))
    -   Adapt to changes in `gix-features` ([`eacb5a4`](https://togithub.com/Byron/gitoxide/commit/eacb5a4))
    -   Add `env::args_os_opt()` which takes an argument to determine input unicode-decomposition ([`a7e606b`](https://togithub.com/Byron/gitoxide/commit/a7e606b))
    -   Release gix-trace v0.1.7, gix-features v0.37.2, gix-commitgraph v0.23.2, gix-traverse v0.36.2, gix-index v0.28.2 ([`b6c04c8`](https://togithub.com/Byron/gitoxide/commit/b6c04c8))
    -   Merge pull request [#&#8203;1248](https://togithub.com/Byron/gitoxide/issues/1248) from joshtriplett/tyop ([`39f35da`](https://togithub.com/Byron/gitoxide/commit/39f35da))
    -   Typo fixes ([`3ef3bc2`](https://togithub.com/Byron/gitoxide/commit/3ef3bc2))
    -   `max-performance-zlib-ng-compat` flag ([`1ba9488`](https://togithub.com/Byron/gitoxide/commit/1ba9488))
    -   Add a max-performance-zlib-ng-compat flag ([`cfb06ec`](https://togithub.com/Byron/gitoxide/commit/cfb06ec))

</details>

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "before 5am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/rust-lang/cargo).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4xNTMuMiIsInVwZGF0ZWRJblZlciI6IjM3LjE1My4yIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIn0=-->
 2024-02-05 19:06:21 +00:00
renovate[bot] eb3a343512
chore(deps): update compatible 2024-02-05 18:07:44 +00:00
Weihang Lo 708e23369e
Bump to 0.79.0 2024-02-04 11:44:00 -05:00
renovate[bot] fcd533a913
chore(deps): update gix 2024-02-01 01:08:02 +00:00
Ed Page bd6b4a9b14 fix(toml): Improve map/sequence error message 
This is a follow up to #13375
 2024-01-31 10:42:58 -06:00
Ed Page c6c1df4758 chore: Make N-2 the default MSRV 
We likely don't want to release these packages every 6 months just for
an MSRV bump.
By moving the MSRV out of the package, `cargo bump-check` will ignore
the MSRV bump.

Inspired by #13266
 2024-01-18 15:30:41 -06:00
Ed Page b291f42dce chore: Make N-0 MSRVs explicit 
This will require a version bump every release but over-releasing these
packages is likely a lot better than over-releasing the N-3 packages,
which we won't have to do anymore after this.

My hope is the `auto` value will be approved and stabilized and then we
won't have to over-release anymore.
 2024-01-18 15:28:04 -06:00
Scott Schafer 0d62ae2fc3
feat: Add rustc style errors for manifest parsing 2023-12-15 13:30:10 -07:00
Tobias Bieniek 6218d08504
crates-io: Bump version to v0.40.0 2024-01-09 18:03:21 +01:00
renovate[bot] 03beda3a6e chore(deps): update msrv 2024-01-08 22:17:07 +00:00
bors 87eb374d49 Auto merge of #13249 - WeiTheShinobi:update_dependency_handlebars, r=epage 
Update dependency handlebars to v5 for mdman.

### What does this PR try to resolve?

issue #13238
- update dependency handlebars 4.5.0 -> 5.0.0
- fix code to fit the changes of Handlebars API
- RenderError::new() is deprecated. Use RenderErrorReason instead

### How should we test and review this PR?
pass all tests in /crates/mdman/tests
 2024-01-04 16:03:50 +00:00
WeiTheShinobi 06201b9892 Update dependency handlebars to v5 for mdman. 
- handlebars 4.5.0 -> 5.0.0
- fix code to fit the changes of Handlebars API
- RenderError::new() is deprecated. Use RenderErrorReason instead
 2024-01-04 22:59:46 +08:00
bors f9946d15df Auto merge of #13241 - epage:syntax, r=Muscraft 
feat(embedded): Add multiple experimental manifest syntaxes

### What does this PR try to resolve?

As syntax discussions for "cargo script" are on-going, this allows us to experiment with a couple of them so we can see how they work in practice.

This is missing the line-prefix syntax as we decide how we want to separate blocks for it.

While doing this, I removed the previous doc-comment syntax.  This was left in for transition purposes.  With where discussions are going, its unlikely we'll go back to that syntax.

### How should we test and review this PR?

### Additional information

rust-lang/rfcs#3503

https://rust-lang.zulipchat.com/#narrow/stream/213817-t-lang/topic/Syntax.20for.20embedded.20tooling.20metadata
 2024-01-03 21:26:07 +00:00
Ed Page 7e5dd711b5 fix(embedded)!: Remove doc comment manifest support 
We added code fence support in ba869d36ed
(September), so I think this was enough of a transition period and there
is little interest in going back to this.
 2024-01-02 16:25:12 -06:00
Weihang Lo 54e83c2969
chore: tracing be compat with rustc_log 
The current version of rustfix cannot be used in rust-lang/rust due
to the dependency on `tracing`. `tracing-core` is currently locked
to 0.1.30, which is too old for the version in the cargo repo
(it looks like they are trying to avoid a known deadlock).

See: https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/rustfix.20is.20incompatible.20with.20rust-lang.2Frust
 2024-01-02 15:32:15 -05:00
renovate[bot] 4deb34bd0b
chore(deps): update compatible 2024-01-02 10:21:24 +00:00
bors add15366ea Auto merge of #13230 - rust-lang:renovate/gix, r=epage 
chore(deps): update gix

[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [gix](https://togithub.com/Byron/gitoxide) | workspace.dependencies | minor | `0.56.0` -> `0.57.1` |
| [gix-features-for-configuration-only](https://togithub.com/Byron/gitoxide) | workspace.dependencies | minor | `0.35.0` -> `0.37.1` |

---

### Release Notes

<details>
<summary>Byron/gitoxide (gix)</summary>

### [`v0.57.1`](https://togithub.com/Byron/gitoxide/releases/tag/gix-v0.57.1): gix v0.57.1

[Compare Source](https://togithub.com/Byron/gitoxide/compare/gix-v0.57.0...gix-v0.57.1)

##### Chore

-   change `rust-version` manifest field back to 1.65.
    They didn't actually need to be higher to work, and changing them
    unecessarily can break downstream CI.

    Let's keep this value as low as possible, and only increase it when
    more recent features are actually used.

##### Commit Statistics

-   2 commits contributed to the release.
-   1 commit was understood as [conventional](https://www.conventionalcommits.org).
-   0 issues like '(#ID)' were seen in commit messages

##### Commit Details

<csr-read-only-do-not-edit/>

<details><summary>view details</summary>

-   **Uncategorized**
    -   Merge branch 'msrv' ([`8c492d7`](https://togithub.com/Byron/gitoxide/commit/8c492d7))
    -   Change `rust-version` manifest field back to 1.65. ([`3bd09ef`](https://togithub.com/Byron/gitoxide/commit/3bd09ef))

</details>

### [`v0.57.0`](https://togithub.com/Byron/gitoxide/releases/tag/gix-v0.57.0): gix v0.57.0

[Compare Source](https://togithub.com/Byron/gitoxide/compare/gix-v0.56.0...gix-v0.57.0)

##### Chore

-   <csr-id-aea89c3ad52f1a800abb620e9a4701bdf904ff7d/> upgrade MSRV to v1.70
    Our MSRV follows the one of `helix`, which in turn follows Firefox.

##### New Features

-   `Repository::rev_parse*()` now supports `branch@{upstream|push|u|p}`.
    Previously it would be parsed, but always error as the implementation didn't exist.
    Now it will return the fetch and push tracking branches respectively.
-   Add `Reference::remote_tracking_ref_name()` and `*::remote_ref_name()`.
    These methods mirror their respective `Repository::branch_*` prefixed versions.
-   add `Repository::branch_remote_tracking_ref_name()`.
-   add `push.default` config key
-   add `config::Snapshot::trusted_program()`.
    That way it's possible to obtain an executable, program or script
    from a key in the configuration that is in a trusted section of the
    configuration.

    This goes along with a new `command` feature that brings in the `command`
    module at the top level to be able to execute such commands.
-   add `clone::PrepareFetch::with_in_memory_config_overrides()`.
    With it one can affect the repository configuration right before fetching.

##### New Features (BREAKING)

-   `Repository::remote_names|remote_default_name()` now returns `Cow<'_, BStr>` instead of `Cow<'_, str>`.
    That way information won't degenerate due to enforcement of UTF-8.

##### Bug Fixes (BREAKING)

-   rename `Repository::branch_remote_ref()` to `Repository::branch_remote_ref_name()`, add `direction` argument (also to `Repository::branch_remote_name()` and `Repository::branch_remote()`).
    This better differentiates the return value from the corresponding ref objects,
    which would require the named ref to exist in the repository.

    The `direction` argument allows to get the reference to push to as well.
    Further, it now takes a full ref name to support deriving the name of branches
    to push to.

    Regarding `Repository::branch_remote()`,  previously, this functionality
    was only available from a `Reference`,
    but now it's more generally available with just a branch name.

    The method was also adjusted to permit looking up non-symbolic remote
    names, like remotes that are specified by their URL.
-   mark `gix::interrupt::init_handler()` as unsafe
    The passed `interrupt()` argument will be called from a signal
    handler, so that needs to be documented and the call sites need to
    state that they fulfill the contract.

    Thanks to [`@&#8203;Manishearth](https://togithub.com/Manishearth)` for pointing this out.

##### Commit Statistics

-   40 commits contributed to the release over the course of 22 calendar days.
-   22 days passed between releases.
-   10 commits were understood as [conventional](https://www.conventionalcommits.org).
-   4 unique issues were worked on: [#&#8203;1158](https://togithub.com/Byron/gitoxide/issues/1158), [#&#8203;1165](https://togithub.com/Byron/gitoxide/issues/1165), [#&#8203;1178](https://togithub.com/Byron/gitoxide/issues/1178), [#&#8203;1191](https://togithub.com/Byron/gitoxide/issues/1191)

##### Thanks Clippy

[Clippy](https://togithub.com/rust-lang/rust-clippy) helped 1 time to make code idiomatic.

##### Commit Details

<csr-read-only-do-not-edit/>

<details><summary>view details</summary>

-   **[#&#8203;1158](https://togithub.com/Byron/gitoxide/issues/1158)**
    -   Remove extra-lines from changelog ([`11c9f66`](https://togithub.com/Byron/gitoxide/commit/11c9f66))
-   **[#&#8203;1165](https://togithub.com/Byron/gitoxide/issues/1165)**
    -   Complete partial note ([`8ef0538`](https://togithub.com/Byron/gitoxide/commit/8ef0538))
-   **[#&#8203;1178](https://togithub.com/Byron/gitoxide/issues/1178)**
    -   Add `config::Snapshot::trusted_program()`. ([`3f84213`](https://togithub.com/Byron/gitoxide/commit/3f84213))
-   **[#&#8203;1191](https://togithub.com/Byron/gitoxide/issues/1191)**
    -   Add note to clarify what users might want to do ([`2e04403`](https://togithub.com/Byron/gitoxide/commit/2e04403))
-   **Uncategorized**
    -   Prepare changelogs of next release ([`e78a92b`](https://togithub.com/Byron/gitoxide/commit/e78a92b))
    -   Merge branch 'maintenance' ([`4454c9d`](https://togithub.com/Byron/gitoxide/commit/4454c9d))
    -   Upgrade MSRV to v1.70 ([`aea89c3`](https://togithub.com/Byron/gitoxide/commit/aea89c3))
    -   Thanks clippy ([`d38d1cc`](https://togithub.com/Byron/gitoxide/commit/d38d1cc))
    -   Merge branch 'tracking-branch' ([`0fe20e8`](https://togithub.com/Byron/gitoxide/commit/0fe20e8))
    -   Refactor ([`530c15d`](https://togithub.com/Byron/gitoxide/commit/530c15d))
    -   `Repository::rev_parse*()` now supports `branch@{upstream|push|u|p}`. ([`3fba5b8`](https://togithub.com/Byron/gitoxide/commit/3fba5b8))
    -   Add `Reference::remote_tracking_ref_name()` and `*::remote_ref_name()`. ([`270322e`](https://togithub.com/Byron/gitoxide/commit/270322e))
    -   Add `Repository::branch_remote_tracking_ref_name()`. ([`4aa4b05`](https://togithub.com/Byron/gitoxide/commit/4aa4b05))
    -   Rename `Repository::branch_remote_ref()` to `Repository::branch_remote_ref_name()`, add `direction` argument (also to `Repository::branch_remote_name()` and `Repository::branch_remote()`). ([`404fde5`](https://togithub.com/Byron/gitoxide/commit/404fde5))
    -   `Repository::remote_names|remote_default_name()` now returns `Cow<'_, BStr>` instead of `Cow<'_, str>`. ([`5c07c76`](https://togithub.com/Byron/gitoxide/commit/5c07c76))
    -   Add `push.default` config key ([`8ac2dcc`](https://togithub.com/Byron/gitoxide/commit/8ac2dcc))
    -   Merge branch 'match_ceiling_dir_or_error' ([`cda5b51`](https://togithub.com/Byron/gitoxide/commit/cda5b51))
    -   Merge branch 'main' into fix-1183 ([`1691ba6`](https://togithub.com/Byron/gitoxide/commit/1691ba6))
    -   Release gix-ref v0.39.1 ([`c1cfe6e`](https://togithub.com/Byron/gitoxide/commit/c1cfe6e))
    -   Merge branch 'patch-1' ([`20dce42`](https://togithub.com/Byron/gitoxide/commit/20dce42))
    -   Differentiate between `Executable` and `Program` ([`56d1d09`](https://togithub.com/Byron/gitoxide/commit/56d1d09))
    -   Add `core.editor` key ([`ff71e07`](https://togithub.com/Byron/gitoxide/commit/ff71e07))
    -   Merge branch 'archive-handling' ([`7549559`](https://togithub.com/Byron/gitoxide/commit/7549559))
    -   Check all git-lfs managed files into the repository ([`35439de`](https://togithub.com/Byron/gitoxide/commit/35439de))
    -   Git-lfs might fail early; let's rely on these caches to be recreated, where possible ([`b6f2b81`](https://togithub.com/Byron/gitoxide/commit/b6f2b81))
    -   Release gix-hash v0.13.3, gix-index v0.27.1 ([`98b08f4`](https://togithub.com/Byron/gitoxide/commit/98b08f4))
    -   Merge branch 'mailmap-config-section' ([`8dda069`](https://togithub.com/Byron/gitoxide/commit/8dda069))
    -   Use new `mailmap` keys and make a few improvements. ([`7f65ffd`](https://togithub.com/Byron/gitoxide/commit/7f65ffd))
    -   Assign more suitable types to `mailmap` keys ([`1bf3e88`](https://togithub.com/Byron/gitoxide/commit/1bf3e88))
    -   Add config section for mailmap.{blob,file}. ([`86c7fa1`](https://togithub.com/Byron/gitoxide/commit/86c7fa1))
    -   Merge branch 'configure-prepare-fetch' ([`281fda0`](https://togithub.com/Byron/gitoxide/commit/281fda0))
    -   Add `clone::PrepareFetch::with_in_memory_config_overrides()`. ([`b5c36b8`](https://togithub.com/Byron/gitoxide/commit/b5c36b8))
    -   Allow overriding Git configuration when cloning. ([`9833b45`](https://togithub.com/Byron/gitoxide/commit/9833b45))
    -   Merge branch 'push-yvzxzqrkkvry' ([`4917beb`](https://togithub.com/Byron/gitoxide/commit/4917beb))
    -   Fixup new unsafe interrupt handler ([`c23bb87`](https://togithub.com/Byron/gitoxide/commit/c23bb87))
    -   Mark `gix::interrupt::init_handler()` as unsafe ([`59b8104`](https://togithub.com/Byron/gitoxide/commit/59b8104))
    -   Reduce size of unsafe block in signal handler ([`d77bc0e`](https://togithub.com/Byron/gitoxide/commit/d77bc0e))
    -   Release gix-config v0.32.1 ([`cd26fd8`](https://togithub.com/Byron/gitoxide/commit/cd26fd8))
    -   Merge branch 'adjustments-for-cargo' ([`56588a9`](https://togithub.com/Byron/gitoxide/commit/56588a9))
    -   Fix import/prevent warning ([`ec0211a`](https://togithub.com/Byron/gitoxide/commit/ec0211a))

</details>

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "before 5am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/rust-lang/cargo).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4xMDMuMSIsInVwZGF0ZWRJblZlciI6IjM3LjEwMy4xIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIn0=-->
 2024-01-02 03:24:42 +00:00
renovate[bot] 37f4a971ca
chore(deps): update gix 2024-01-01 03:52:17 +00:00
Eric Huss a21997f0cc rustfix: Support inserting new lines. 
If rustfix received a suggestion which inserts new lines without
replacing existing lines, it would ignore the suggestion. This is
because `parse_snippet` would immediately return if the `lines` to
replace was empty.

The solution here is to just drop the code which messes with the
original text line. `cargo fix` (and compiletest) currently do not use
this. This was originally added back in the days when rustfix supported
an interactive UI which showed color highlighting of what it looks like
with the replacement. My feeling is that when we add something like this
back in, I would prefer to instead use a real diff library and display
instead of trying to do various text manipulation for display. This
particular code has generally been buggy, and has been a problem several
times.

The included test fails without this fix because the changes do not
apply, and the code cannot compile.
 2023-12-31 10:18:22 -08:00
Weihang Lo 49ada9f092
Bump to 0.78.0 2023-12-21 16:08:24 -05:00
bors a9c749c33e Auto merge of #13186 - weihanglo:cargo-util-schemas-error-types, r=epage 
refactor: custom error types for `cargo-util-schemas`
 2023-12-20 15:52:40 +00:00
Weihang Lo 0b0e78fa3f
chore: bump cargo-util-schemas to 0.2.0 2023-12-20 10:38:03 -05:00
bors c21be2b7cf Auto merge of #13168 - leonzchang:handlebars-v4, r=epage 
chore(deps): update rust crate handlebars to `v4.5.0`

In the latest version of `handlebars`, rules for whitespace auto elimination is to check if the directive `{{# xxx}}`` and ``{{/ xxx}}` is holding a whole line, with leading and trailing whitespaces counted, and then remove the trailing NEWLINE (See [`template.rs`](9d7d555628/src/template.rs (L568-L889))).

```md
{{#options}}
                              <--- this newline will be removed after a standalone block
{{#option "`-o` _outdir_"}}
                              <--- this newline will be removed
Some content

{{/option}}
                              <--- this newline will be removed
{{/options}}
                              <--- this newline will be removed
```

This PR changes includes (fixes #13162):
1. update `handlebars` crate to `v4.5.0`.
2. add extra NEWLINE to helper blocks `options`, `option` to align with the new strip rules, preserving the original behavior.
3. update doc(the rest handlebars expression) to align with the new strip rules..
 2023-12-20 14:52:29 +00:00
leonzchang b96b244c28
update handlebars & fix tests & update doc 2023-12-20 11:12:49 +08:00
Weihang Lo 8a762b89b9
refactor: link homepage to The Cargo Book for main cargo crate 2023-12-18 16:09:08 -05:00
Weihang Lo ad2c45bde9
refactor: clean up package metadata 
Like PR 12352 but for homepage and repository

Versions for

* `cargo-credential-1password`
* `cargo-util-schemas`
* `home`

are bumped along with the change.
 2023-12-18 16:09:03 -05:00
Ed Page 633929d3aa refactor(schemas): Pull out cargo-util-schemas crate 
Fixes #12801
 2023-12-15 13:22:25 -06:00
Weihang Lo 62bf43294f
chore: downgrade to openssl v1.1.1 
riscv64 detection bug is fixed but is not released (openssl/openssl#22871)
See also https://github.com/rust-lang/rust/pull/119007#issuecomment-1859231819
 2023-12-17 12:37:13 -05:00
bors 0e18edfb82 Auto merge of #13159 - heiher:bump-openssl, r=weihanglo 
chore(deps): update rust crate openssl to 0.10.61

### What does this PR try to resolve?

Bump rust crate `openssl` to `0.10.61`.

This is a major bump that Cargo starts depending on OpenSSL v3 via [openssl-src@300.1.2+3.1.1](https://crates.io/crates/openssl-src/300.1.2+3.1.1)

Some other notes:

* OpenSSL 3.1.1 was released on [2023-05-30](https://github.com/openssl/openssl/blob/master/CHANGES.md#changes-between-310-and-311-30-may-2023).
* Starting from 1.6 [libgit2 supports OpenSSL v3](https://github.com/libgit2/libgit2/blob/main/docs/changelog.md#v16)
* Starting from 1.10.0 [libssh2 supports OpenSSL v3](https://libssh2.org/changes.html#1.10.0)
* OpenSSL 1.1.1 [is EOL](https://www.openssl.org/blog/blog/2023/03/28/1.1.1-EOL/).
* curl seems to support OpenSSL v3 before it got released.

### How should we test and review this PR?

Build test.

### Additional information

The openssl build issue for loongarch is resolved.
 2023-12-12 18:58:15 +00:00
bors 7c722f76ed Auto merge of #13134 - arlosi:vendor-libgit2, r=ehuss 
`all-static` feature should include `vendored-libgit2`

Cargo has an `all-static` feature which is supposed to statically link dependencies for distributing.

However, it doesn't include `libgit2`. If the system has a compatible version of `libgit2` and `pkg-config` installed, then the `all-static` build will still use the system `libgit2`.
 2023-12-12 17:50:31 +00:00
WANG Rui 8e9a62d51e chore(deps): update rust crate openssl to 0.10.61 2023-12-12 21:29:45 +08:00
Eric Huss 4e17e02cb9 Update curl-sys to bring in curl 8.5.0 2023-12-09 15:58:23 -08:00
Ed Page ad2643d8e2 fix: Print rustc messages colored on wincon 
Fixes #13104
 2023-12-08 11:49:05 -06:00
Arlo Siemsen 1a90797c0a all-static feature includes vendored-libgit2 2023-12-07 19:23:33 -06:00
Sebastian Thiel 50c0005a28
upgrade gitoxide to v0.56 (#11821) 
This release disables stderr for external programs by default, while
allowing to override these settings using configuration or environment
variables.
 2023-12-06 17:09:08 +01:00
Weihang Lo df34bdd8d7
Revert "chore(deps): update rust crate openssl to 0.10.60 [security]" 
Reverts rust-lang/cargo#13068

`openssl@0.10.160` switches to OpenSSL v3,
which causes Cargo build failure on loongarch64.

See <https://github.com/rust-lang/rust/pull/118541#issuecomment-1837197918>
 2023-12-02 11:41:57 -05:00