Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: rust-lang/regex
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 1.12.2
Choose a base ref
...
head repository: rust-lang/regex
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 1.12.3
Choose a head ref
  • 6 commits
  • 13 files changed
  • 3 contributors

Commits on Feb 3, 2026

  1. automata: fix onepass::DFA::try_search_slots panic when too many sl… 

    …ots are given

The API specifically documents that the caller may provide *any* number
of slots. But the onepass implementation was panicking when too many
were provided. (I had only considered the case when too few were
provided when I wrote one-pass implementation I think.)

This already works for the PikeVM and the bounded backtracker. This
commit adds tests covering those as well.

Note that the bug report specifically cites a zero-repetition capture
group as the instigator here. While that may have provided the
circumstances for the bug to appear, the actual bug is more general than
that. You don't need any capture groups at all to provoke it. You just
need to provide more slots than there are in the compiled regex.

Fixes #1327, Closes #1329
    @keith-hall @BurntSushi
    keith-hall authored and BurntSushi committed Feb 3, 2026
    Configuration menu
    Copy the full SHA
    4733e28 View commit details
    Browse the repository at this point in the history

  2. cargo: exclude development scripts and fuzzing data 

    During a dependency review we noticed that different regex-* crate
includes various development scripts and sometimes fuzzing data. These
development scripts shouldn't be there as they might, at some point
become problematic. As of now they prevent any downstream user from
enabling the `[bans.build.interpreted]` option of cargo deny. The
fuzzing data are also not needed for anything.

I opted for using an explicit include list instead of an exclude list
to prevent these files from beeing included in the published packages
to make sure that everything that's included is an conscious choice.

Closes #1319
    @weiznich @BurntSushi
    weiznich authored and BurntSushi committed Feb 3, 2026
    Configuration menu
    Copy the full SHA
    6a81006 View commit details
    Browse the repository at this point in the history

  3. regex-lite-0.1.9

    @BurntSushi
    BurntSushi committed Feb 3, 2026
    Configuration menu
    Copy the full SHA
    0c07fae View commit details
    Browse the repository at this point in the history

  4. regex-syntax-0.8.9

    @BurntSushi
    BurntSushi committed Feb 3, 2026
    Configuration menu
    Copy the full SHA
    a3433f6 View commit details
    Browse the repository at this point in the history

  5. regex-automata-0.4.14

    @BurntSushi
    BurntSushi committed Feb 3, 2026
    Configuration menu
    Copy the full SHA
    5e195de View commit details
    Browse the repository at this point in the history

  6. 1.12.3

    @BurntSushi
    BurntSushi committed Feb 3, 2026
    Configuration menu
    Copy the full SHA
    b028e4f View commit details
    Browse the repository at this point in the history
Loading