Skip to content

Adopt plaintext fences for prose output (#161) #176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
leynos merged 2 commits into from
Jul 26, 2026
+21 −3
Merged

Adopt plaintext fences for prose output (#161) #176

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
29441fd
Use plaintext for prose fence blocks (#161)
Jul 14, 2026
cff9ccc
Refresh generated spelling configuration
Jul 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/users-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,7 @@ all git-tracked `Cargo.lock` files are fresh under `--locked` mode. If any
lockfile is stale — for example after a `lading bump` that regenerated a nested
workspace lockfile — the command exits with code 1 and prints a repair command:

```text
```plaintext
Tracked Cargo.lock files are stale after manifest version changes.
Run the following to repair:
cargo generate-lockfile --manifest-path <path>/Cargo.toml
Expand Down Expand Up @@ -162,7 +162,7 @@ even in dry-run mode. When two or more workspace crates are released together
for the first time and one depends on another at a version that is not yet on
crates.io, `cargo package` will fail with an error similar to:

```text
```plaintext
error: failed to prepare local package for uploading

Caused by:
Expand Down Expand Up @@ -292,7 +292,7 @@ inconsistent: the manifests carry the new version but the affected lockfiles do
not. When several lockfiles are regenerated, `lading` raises one aggregated
error that lists every failed manifest with the exact repair command to run:

```text
```plaintext
Cargo lockfile regeneration failed for 2 manifest(s). Manifests already carry the new version, so the workspace is inconsistent until each lockfile below is repaired:
- Cargo lockfile regeneration failed for crates/a/Cargo.toml with exit code 101: <cargo error>
cargo update --workspace --manifest-path crates/a/Cargo.toml
Expand Down
18 changes: 18 additions & 0 deletions typos.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1699,6 +1699,24 @@ extend-ignore-re = [
"pluralizers" = "pluralizers"
"pluralizes" = "pluralizes"
"pluralizing" = "pluralizing"
"polymerisable" = "polymerizable"
"polymerisation" = "polymerization"
"polymerisations" = "polymerizations"
"polymerise" = "polymerize"
"polymerised" = "polymerized"
"polymeriser" = "polymerizer"
"polymerisers" = "polymerizers"
"polymerises" = "polymerizes"
"polymerising" = "polymerizing"
"polymerizable" = "polymerizable"
"polymerization" = "polymerization"
"polymerizations" = "polymerizations"
"polymerize" = "polymerize"
"polymerized" = "polymerized"
"polymerizer" = "polymerizer"
"polymerizers" = "polymerizers"
"polymerizes" = "polymerizes"
"polymerizing" = "polymerizing"
"popularisable" = "popularizable"
"popularisation" = "popularization"
"popularisations" = "popularizations"
Expand Down
Loading