Skip to content
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.

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

Update Rust crate grep to 0.3 #6

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update Rust crate grep to 0.3 #6

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 27, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
grep (source) dependencies minor 0.2 -> 0.3

Release Notes

BurntSushi/ripgrep (grep)

v0.3.1

Compare Source

=====
Bug fixes:

  • BUG #​242:
    ripgrep didn't respect --colors foo:none correctly. Now it does.

v0.3.0

Compare Source

=====
This is a new minor version release of ripgrep that includes two breaking
changes with lots of bug fixes and some new features and performance
improvements. Notably, if you had a problem with colors or piping on Windows
before, then that should now be fixed in this release.

BREAKING CHANGES:

  • ripgrep now requires Rust 1.11 to compile. Previously, it could build on
    Rust 1.9. The cause of this was the move from
    Docopt to Clap
    for argument parsing.
  • The -e/--regexp flag can no longer accept a pattern starting with a -.
    There are two work-arounds: rg -- -foo and rg [-]foo or rg -e [-]foo
    will all search for the same -foo pattern. The cause of this was the move
    from Docopt to Clap
    for argument parsing.
    This may get fixed in the
    future.
    .

Performance improvements:

  • PERF #​33:
    ripgrep now performs similar to GNU grep on small corpora.
  • PERF #​136:
    ripgrep no longer slows down because of argument parsing when given a large
    argument list.

Feature enhancements:

  • Added or improved file type filtering for Elixir.
  • FEATURE #​7:
    Add a -f/--file flag that causes ripgrep to read patterns from a file.
  • FEATURE #​51:
    Add a --colors flag that enables one to customize the colors used in
    ripgrep's output.
  • FEATURE #​138:
    Add a --files-without-match flag that shows only file paths that contain
    zero matches.
  • FEATURE #​230:
    Add completion files to the release (Bash, Fish and PowerShell).

Bug fixes:

  • BUG #​37:
    Use correct ANSI escape sequences when TERM=screen.linux.
  • BUG #​94:
    ripgrep now detects stdin on Windows automatically.
  • BUG #​117:
    Colors should now work correctly and automatically inside mintty.
  • BUG #​182:
    Colors should now work within Emacs. In particular, --color=always will
    emit colors regardless of the current environment.
  • BUG #​189:
    Show less content when running rg -h. The full help content can be
    accessed with rg --help.
  • BUG #​210:
    Support non-UTF-8 file names on Unix platforms.
  • BUG #​231:
    Switch from block buffering to line buffering.
  • BUG #​241:
    Some error messages weren't suppressed when --no-messages was used.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title Update Rust crate grep to 0.3 Update Rust crate grep to 0.3.1 May 1, 2024
@renovate renovate bot changed the title Update Rust crate grep to 0.3.1 Update Rust crate grep to 0.3 May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants