## Summary

- Drop a duplicated verb in the note about enumerating rule names: "we
strongly recommend **including suppressing** specific rules" → "we
strongly recommend **including** specific rules".
- Make the "Multiple suppressions comments" heading match its siblings
("ty suppression comments", "Standard suppression comments", "Unused
suppression comments"): "Multiple suppression**s** comments" → "Multiple
suppression comments". No other docs link to this anchor, so this rename
is safe.


---------

Co-authored-by: Micha Reiser <micha@reiser.io>

## Summary

Adds a short note to the Emacs section of the editor integration docs
explaining how Flycheck users can route ty's diagnostics through the
[flycheck-eglot](https://github.com/flycheck/flycheck-eglot) bridge.

The current Eglot snippet (added in #3107) covers the simple case, but
the original request in #2902 specifically asked about Flycheck-based
setups. This adds the minimal additional snippet for that path without
changing the existing recommended setup. Modeled on the multi-subsection
layout used by Ruff's [Emacs
docs](https://docs.astral.sh/ruff/editors/setup/#emacs).

Refs #2902.

## Test Plan

- `mdformat docs/editors.md --check` passes
- `markdownlint-cli@0.48.0 docs/editors.md` passes
- Verified `flycheck/flycheck-eglot` is the official upstream package

---------

Co-authored-by: Dhruv Manilawala <dhruvmanila@gmail.com>

…t calls (#3523)

## Summary

`main()` in `scripts/update_schemastore.py` calls `check_output` twice
to read
git SHAs — once for the expected ruff submodule revision and once for
the actual
HEAD of the submodule — but neither call passes `text=True`. Without it,
`check_output` returns `bytes`, and when those values are interpolated
into the
mismatch warning f-string the user sees raw bytes repr in their
terminal:

    The ruff submodule is at b'def456...' but main expects b'abc123...'

instead of the intended:

    The ruff submodule is at def456... but main expects abc123...

The same `main()` already uses `text=True` correctly for the
`current_sha`
call on line 81. This PR makes the two revision-check calls consistent
with
that pattern.

---------

Co-authored-by: Dhruv Manilawala <dhruvmanila@gmail.com>

…3532)

## Summary

- Closes #2937.
- Adds `:language-id "python"` to the Eglot `eglot-server-programs`
entry in the Emacs editor-integration docs so the recommended snippet
works out of the box.
- Eglot derives the LSP `languageId` from the major-mode symbol, so the
previous `python-base-mode` entry caused Eglot to advertise documents as
`python-base`. The ty server only accepts the `python` language id
([`text_document.rs`](https://github.com/astral-sh/ruff/blob/main/crates/ty_server/src/document/text_document.rs)),
so users were silently getting no diagnostics.
- Adds a short prose note explaining the constraint, so readers who copy
the snippet (or adapt it for a different mode) understand why the entry
is shaped this way. Fix matches the one suggested upstream in
[eglot#1580](joaotavora/eglot#1580).

## Test plan

- [x] Visually proof the rendered Markdown
- [x] Verified the snippet shape against the eglot discussion accepted
answer

---------

Co-authored-by: Dhruv Manilawala <dhruvmanila@gmail.com>

I was already halfway through a review when @charliermarsh merged the
latest release PR -- too fast for me ⚡️

## Summary

Make sure that the lockfile is not corrupted when uv's default config
points to a company mirror. Tested by running `./scripts/release.sh` in
an environment where the lockfile was previously corrupted.