Abby Mitchell

This commit **refactors** the **`pyrefly` reporting command's suppression parsing logic** to support a wider array of tools. It replaces the previous hardcoded regex parser in `report.rs` with a new multi-tool `pyrefly_python::ignore::Ignore` parser, enabling recognition of suppression comments from seven different sources like `# type: ignore` and `# mypy: type: ignore`. This **enhancement** renames the `Suppression` struct to `ReportSuppression` and updates its `kind` field to store the originating tool name, significantly improving the accuracy and detail of the **`pyrefly` report**. The change also removes the `regex` crate dependency, streamlining the module.

This commit introduces an **automated system for generating Pyrefly release notes**, significantly **streamlining the release management process**. It adds new **scripting utilities** (`scripts/generate_release_notes.py`, `scripts/github_utils.py`) that interact with the **GitHub API** to gather relevant data like commits, contributors, and closed issues between specified Git references. An **LLM** then uses this data, along with a defined prompt and template (`release_notes/`), to produce polished markdown release notes. This **new capability** reduces manual effort and ensures consistency in future release documentation by automating data collection and content generation.

This commit introduces a **new automated release workflow** within **GitHub Actions** to streamline the project's release process. It adds a `create_release.yml` workflow that automatically creates a GitHub Release with structured release notes (from `release_notes/release-notes-v{version}.md`) and sends a Discord notification upon a new version being published to PyPI. The existing `publish_to_pypi.yml` workflow is modified to trigger this new release creation and notification step after successfully pushing a version tag. This **enhances CI/CD automation** by ensuring consistent release documentation and immediate communication for new software versions, building upon previous work for release note generation.

This commit introduces a **bug fix** to the **`pyrefly` reporting mechanism** to correctly handle Python stub files. It implements new logic within `pyrefly/lib/commands/report.rs`, specifically the `merge_uncovered_py_symbols` function, to **merge uncovered symbols from Python source files into their corresponding stub file reports**. This enhancement ensures **accurate completeness metrics** are generated when analyzing projects that utilize `.pyi` stub files, preventing misleading reports. New test files (`partial_stub.py`, `partial_stub.pyi`, `partial_stub.expected.json`) have been added to validate this improved stub merging logic.

This commit implements a **new feature** for the `pyrefly` reporting tool, introducing a **type annotation completeness metric**. It calculates the percentage of functions that are fully annotated, based on return types and all non-`self`/`cls` parameter annotations, providing both **per-file** and **aggregate scores**. This enhancement to the `pyrefly` report command (`pyrefly/lib/commands/report.rs`) offers users valuable insights into their codebase's type coverage, with the `website/docs/report.mdx` documentation and the report's JSON output structure updated accordingly.

This commit introduces **new type completeness metrics** to the `pyrefly report` command, significantly enhancing its ability to assess code quality. It now distinguishes between **annotation completeness** (presence of type hints) and **type completeness** (absence of `Any` in resolved types), providing insights similar to Pyright's `--verifytypes`. The **`pyrefly report` JSON output** is updated to include these metrics per-file, per-function, and per-parameter, along with aggregate summaries. This **enhancement** provides developers with a comprehensive view of their codebase's type coverage and resolution quality, aiding in maintaining robust and well-typed Python projects. Additionally, the **documentation** for the coverage report has been updated to reflect these new metrics.

This commit **adds new documentation content** to the project's **website blog**, publishing a new post titled "Python Typechecker Comparison: Empty Container Inference". This **content addition** provides valuable insights into how different Python type checkers handle empty container inference, located at `website/blog/2026-02-25-container-inference-comparison.md`. The work also involves a minor **maintenance update** to the `website/blog/authors.yml` configuration to include a new author, Jia Chen. This expands the available educational resources for users interested in Python type checking.

This commit **updates and reorganizes** the **project's contributing guide** (`CONTRIBUTING.md`) to provide clearer expectations and a more intuitive flow for potential contributors. It **expands the documentation** with new sections covering essential topics such as getting started, choosing issues, making pull requests, and specific guidelines for AI-generated code. This **documentation enhancement** aims to streamline the contribution process, improve the quality of community submissions, and ultimately enhance the **contributor experience** by offering comprehensive and well-structured guidance.

This commit **adds new documentation content** to the project's **website blog**, preparing for the publication of a post on February 17th. It introduces a new blog post, `2026-02-17-stubs.md`, which details the bundling of **third-party stubs with Pyrefly**. Concurrently, a **chore** update to `website/blog/authors.yml` adds 'John Van Schultz' as a new author. This **new content** serves to inform the community about a specific **Pyrefly feature**, enhancing the project's public-facing documentation and communication regarding its capabilities.

This commit **adds a new blog post** to the project's website, specifically located at `website/blog/2026-02-06-performance-improvements.mdx`. This **documentation update** details **recent performance improvements** that have been implemented within the **Pyrefly diagnostics** system. The new content serves to inform the community about enhancements to a critical subsystem, highlighting ongoing efforts to optimize its efficiency. This addition provides valuable context and transparency regarding the project's development and the improved capabilities of **Pyrefly diagnostics**.

This commit **adds a new blog post** to the **website's documentation**, specifically detailing "4 Pyrefly Type Narrowing Patterns that make type checking more intuitive" in `website/blog/2026-01-26-narrowing.md`. This **content addition** provides new educational resources for users of the **Pyrefly type checker**, enhancing their understanding of advanced type usage. Concurrently, the `website/blog/authors.yml` file is updated to include Danny Yang as a new blog author. This **documentation update** improves the discoverability and understanding of **Pyrefly's type narrowing capabilities** for the community.

This commit **fixes a bug** in the **LSP auto-import functionality** within `pyrefly`, addressing an issue where suggestions failed to include re-exported symbols from parent packages. Specifically, the `should_include_reexports` function in `pyrefly/lib/state/lsp.rs` is extended to recognize re-exports from parent directories, ensuring that preferred, shorter import paths (e.g., `pydantic` instead of `pydantic.main`) are offered. The auto-import suggestion list is now also sorted to **prioritize these shorter import paths**, significantly improving the accuracy and idiomatic quality of import suggestions for users. This **enhancement** provides a more intuitive and efficient coding experience by presenting the most appropriate import options first.

This commit **updates the documentation** for **IDE features** by restoring the "go to type definition" video, which was previously missing from the relevant page. This **documentation maintenance** ensures that users have a complete visual guide for understanding this specific IDE functionality. The change directly improves the user experience by providing comprehensive resources for developers learning about the IDE's capabilities.

This commit performs **documentation maintenance** by **fixing a broken YouTube video link** in the introductory paragraph of the **Pydantic blog post** (`website/blog/2025-12-03-pyrefly-pydantic.md`). Concurrently, it **standardizes bullet point formatting** within the same article, enhancing overall readability. This **bug fix** and minor **refactoring** ensures that readers have access to the correct video resource and benefit from a more consistent and polished presentation of the blog content.

This commit **introduces a new blog post** to the **Pyrefly website**, specifically documenting the **experimental Pydantic integration** within the framework. This **documentation update** provides users with detailed insights into leveraging Pydantic for data validation and serialization with Pyrefly. To support this new content, the `website/blog/authors.yml` file is also updated to include new author entries for Zeina Migeed and Rebecca Chen. This work primarily serves as a **feature announcement and explanation**, enhancing the project's user-facing documentation.

This commit **updates the version number** for the **`pyrefly`** project from `0.43.1` to `0.44.0`. This is a **maintenance chore** that specifically modifies the `VERSION` constant within the `version.bzl` file. The manual increment signifies a new release or development iteration for the **`pyrefly`** library, potentially impacting downstream dependencies or users who rely on its specific version.

This commit **fixes a broken preview image** for the **Pyrefly beta release blog post**. It **updates the image URL** within the metadata of the `website/blog/2025-11-17-pyrefly-beta.mdx` file to the correct path. This **bug fix** addresses a display issue affecting the **blogging platform's** preview functionality. The change ensures that the appropriate visual asset is displayed when the blog post is shared or previewed, thereby improving the overall presentation and **user experience** for the **Pyrefly beta release** announcement.

This commit **adds a new blog post** to the **website's blog section** announcing the **beta release of Pyrefly**. The new post, located at `website/blog/2025-11-17-pyrefly-beta.mdx`, details the project's features, recent improvements, and future development plans. This is a **documentation update** that serves as a key **announcement** for the Pyrefly community. It informs users about the availability and scope of the beta, providing essential information for early adopters and interested parties.

This commit **enhances the Pydantic documentation** within `website/docs/pydantic.mdx` to explicitly detail the features supported by `pyrefly`. It introduces new sections and examples that clarify capabilities such as field constraints, root models, and alias validation. This **documentation update** serves as a **maintenance** task, providing users with a more comprehensive and explicit understanding of Pydantic integration, thereby improving usability and reducing potential confusion.

This commit **removes the typing survey banner** from the **website's frontend display**. This **maintenance** task is performed in anticipation of the survey's closure, ensuring that users are not presented with outdated information. The change affects the **user interface** of the website, improving the user experience by streamlining the visual presentation and removing a no-longer-relevant call to action.