SIGN IN SIGN UP
astral-sh / ruff UNCLAIMED

An extremely fast Python linter and code formatter, written in Rust.

TAGS

20 tags
0.15.8

Release 0.15.8 (#24217) - **changelog** - **everything else**

0.15.5

Bump 0.15.5 (#23743) Co-authored-by: Brent Westbrook <36778786+ntBre@users.noreply.github.com>

0.15.4

Bump 0.15.4 (#23595) Just to be sure, I ran the example from #23587 again on this branch: ```console ~/astral/ruff on  brent/0.15.4 [$] is 📦 v0.15.4 via 🐍 v3.14.2 via 🦀 v1.93.0 ❯ echo 'x = id' | uvx ruff@latest --isolated check - --preview --select ANN003,PLR1712 error: Ruff crashed. If you could open an issue at: https://github.com/astral-sh/ruff/issues/new?title=%5BPanic%5D ...quoting the executed command, along with the relevant file contents and `pyproject.toml` settings, we'd be very appreciative! thread 'main' (1681253) panicked at crates/ruff_python_semantic/src/definition.rs:285:26: index out of bounds: the len is 0 but the index is 0 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ~/astral/ruff on  brent/0.15.4 [$] is 📦 v0.15.4 via 🐍 v3.14.2 via 🦀 v1.93.0 ❯ echo 'x = id' | just run --isolated check - --preview --select ANN003,PLR1712 cargo run -p ruff -- --isolated check - --preview --select ANN003,PLR1712 Compiling ruff_python_semantic v0.0.0 (/home/brent/astral/ruff/crates/ruff_python_semantic) Compiling ruff v0.15.4 (/home/brent/astral/ruff/crates/ruff) Compiling ruff_linter v0.15.4 (/home/brent/astral/ruff/crates/ruff_linter) Compiling ruff_graph v0.1.0 (/home/brent/astral/ruff/crates/ruff_graph) Compiling ruff_workspace v0.0.0 (/home/brent/astral/ruff/crates/ruff_workspace) Compiling ruff_markdown v0.0.0 (/home/brent/astral/ruff/crates/ruff_markdown) Compiling ruff_server v0.2.2 (/home/brent/astral/ruff/crates/ruff_server) Finished `dev` profile [unoptimized + debuginfo] target(s) in 23.14s Running `target/debug/ruff --isolated check - --preview --select ANN003,PLR1712` warning: Detected debug build without --no-cache. All checks passed! ```

0.15.2

Hard code workflow name and `cancel-in-progress` only for PRs (#23431) This changes the names of concurrency groups in most of our workflows to use their hard-coded names instead of the name of the workflow that triggered them (e.g. `build-wasm-...` and `build-binaries-...` instead of `Release -...` for both). Hopefully this will reduce the number of times the jobs butt heads. I did not make this change for the CI workflow or for the Daily Fuzz workflow since it didn't seem relevant for those, but let me know if I should.

0.15.1

Prepare for 0.15.1 (#23253) - **Changelog** - **Everything else** --------- Co-authored-by: Brent Westbrook <36778786+ntBre@users.noreply.github.com>

0.14.14

Prepare release v0.14.14 (#22813)

0.14.13

[ty] Make `NamedTuple(...)` and `namedtuple(...)` calls stricter (#22601) ## Summary Closes https://github.com/astral-sh/ty/issues/2513.

0.14.9

Prepare 0.14.9 release (#21927) - **Changelog and docs** - **metadata**

0.14.3

Bump v0.14.3 (#21152) - **Upgrade to rooster==0.1.1** - **Changelog for v0.14.3** - **Bump v0.14.3**