[stable] 1.44.1 release

[Mark-Simulacrum]

See release notes for details (or commits).

[Mark-Simulacrum]

Hm so I'm having trouble updating just rustfmt-nightly. AFAICT the lockfile upstream didn't change at all, except for the version, in the submodule bump here. But when I try to update things locally, I get

$ cargo update -p rustfmt-nightly --dry-run
    Updating crates.io index
      Adding ena v0.14.0
      Adding psm v0.1.8
      Adding rustc-ap-arena v659.0.0
      Adding rustc-ap-graphviz v659.0.0
      Adding rustc-ap-rustc_ast v659.0.0
      Adding rustc-ap-rustc_ast_passes v659.0.0
      Adding rustc-ap-rustc_ast_pretty v659.0.0
      Adding rustc-ap-rustc_attr v659.0.0
      Adding rustc-ap-rustc_data_structures v659.0.0
      Adding rustc-ap-rustc_errors v659.0.0
      Adding rustc-ap-rustc_expand v659.0.0
      Adding rustc-ap-rustc_feature v659.0.0
      Adding rustc-ap-rustc_fs_util v659.0.0
      Adding rustc-ap-rustc_index v659.0.0
      Adding rustc-ap-rustc_lexer v659.0.0
      Adding rustc-ap-rustc_macros v659.0.0
      Adding rustc-ap-rustc_parse v659.0.0
      Adding rustc-ap-rustc_session v659.0.0
      Adding rustc-ap-rustc_span v659.0.0
      Adding rustc-ap-rustc_target v659.0.0
      Adding rustc-ap-serialize v659.0.0
      Adding rustfmt-config_proc_macro v0.2.0
    Updating rustfmt-nightly v1.4.14 (/home/mark/Edit/rust-2/src/tools/rustfmt) -> v1.4.16
      Adding rustfmt-nightly v1.4.17
      Adding stacker v0.1.9
warning: not updating lockfile due to dry run

I would expect that to just update rustfmt-nightly. Could someone from the cargo team (@ehuss?) or perhaps in the rustfmt world advise?

[ehuss]

I don't know why cargo update is misbehaving. It is probably because RLS uses the [patch] table for rustfmt. The following should do as a workaround:

cargo update -p rustfmt-nightly
cargo update -p rustfmt-nightly:1.4.17 --precise 1.4.16

The second call should revert the RLS to the in-tree copy, and undo the mess the first call makes.

[ehuss]

Filed rust-lang/cargo#8355 for the update issue.

[Mark-Simulacrum]

@bors r+ p=1000 rollup=never

Preparing artifacts for release on Thursday next week.

[bors]

📌 Commit 7b2237e has been approved by Mark-Simulacrum

[bors]

⌛ Testing commit 7b2237e with merge 97f7d1cf031be97311289120e23a8d922de74504...

[bors]

💔 Test failed - checks-azure

[Dylan-DPC-zz]

@bors retry p=1000

[bors]

⌛ Testing commit 7b2237e with merge 6c252f1223c4fca223e116dceff1cb688f0ce715...

[bors]

💔 Test failed - checks-azure

[Dylan-DPC-zz]

@bors retry p=999

(just so that it runs automatically if things are fine, and doesn't if the tree remains closed)

[bors]

⌛ Testing commit 7b2237e with merge e66a24895830bdbb6ed3710b206a87e97883b781...

[bors]

💔 Test failed - checks-azure

[ehuss]

Hm, I should have noticed this will need #73213.

[Mark-Simulacrum]

@bors r+ rollup=never

Thanks! Accepted that PR for beta backport as well.

[bors]

📌 Commit 9592e67 has been approved by Mark-Simulacrum

[bors]

⌛ Testing commit 9592e67 with merge d107792...

[bors]

☀️ Test successful - checks-azure
Approved by: Mark-Simulacrum
Pushing d107792 to stable...