@@ -130,7 +130,6 @@ Each new feature described below should explain how to use it.
130130* Other
131131 * [ gitoxide] ( #gitoxide ) --- Use ` gitoxide ` instead of ` git2 ` for a set of operations.
132132 * [ script] ( #script ) --- Enable support for single-file ` .rs ` packages.
133- * [ lockfile-path] ( #lockfile-path ) --- Allows to specify a path to lockfile other than the default path ` <workspace_root>/Cargo.lock ` .
134133 * [ native-completions] ( #native-completions ) --- Move cargo shell completions to native completions.
135134 * [ warnings] ( #warnings ) --- controls warning behavior; options for allowing or denying warnings.
136135 * [ Package message format] ( #package-message-format ) --- Message format for ` cargo package ` .
@@ -1766,43 +1765,6 @@ will prefer the value in the configuration. The allows Cargo to add new built-in
17661765path bases without compatibility issues (as existing uses will shadow the
17671766built-in name).
17681767
1769- ## lockfile-path
1770-
1771- * Original Issue: [ #5707 ] ( https://github.com/rust-lang/cargo/issues/5707 )
1772- * Tracking Issue: [ #14421 ] ( https://github.com/rust-lang/cargo/issues/14421 )
1773-
1774- The ` -Zlockfile-path ` flag enables the ` resolver.lockfile-path ` configuration option,
1775- which allows you to specify the path of the lockfile ` Cargo.lock ` .
1776-
1777- By default, lockfile is written into ` <workspace_root>/Cargo.lock ` .
1778- However, when sources are stored in read-only directory,
1779- most of the cargo commands would fail when trying to write a lockfile.
1780- This configuration makes it easier to work with readonly sources.
1781-
1782- Note, that currently path must end with ` Cargo.lock ` .
1783- If you want to use this feature in multiple projects,
1784- lockfiles should be stored in different directories.
1785-
1786- ### Documentation updates
1787-
1788- * as a new ` resolver.lockfile-path ` entry in config.md*
1789-
1790- * Keep in mind, the ` [resolver] ` section has this clarification:*
1791-
1792- > * The ` [resolver] ` table overrides dependency resolution behavior for local development (e.g. excludes ` cargo install ` ).*
1793-
1794- #### ` resolver.lockfile-path `
1795-
1796- * Type: string (path)
1797- * Default: ` <workspace_root>/Cargo.lock `
1798- * Environment: ` CARGO_RESOLVER_LOCKFILE_PATH `
1799-
1800- Specifies the path to the lockfile.
1801- By default, the lockfile is written to ` <workspace_root>/Cargo.lock ` .
1802- This option is useful when working with read-only source directories.
1803-
1804- The path must end with ` Cargo.lock ` .
1805-
18061768## native-completions
18071769* Original Issue: [ #6645 ] ( https://github.com/rust-lang/cargo/issues/6645 )
18081770* Tracking Issue: [ #14520 ] ( https://github.com/rust-lang/cargo/issues/14520 )
@@ -2353,3 +2315,7 @@ See the [`include` config documentation](config.md#include) for more.
23532315## pubtime
23542316
23552317The ` pubtime ` index field has been stabilized in Rust 1.94.0.
2318+
2319+ ## lockfile-path
2320+
2321+ Support for ` resolver.lockfile-path ` config field has been stabilized in Rust 1.97.0.
0 commit comments