Skip to content

fix: Interpret package name as a string instead of Regex when using grep #68

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

Merged
merged 2 commits into from
May 2, 2025

Conversation

laur89
Copy link

@laur89 laur89 commented Apr 23, 2025

  • package name to grep should be interpreted as a fixed string, not as regex. the danger for collision is small, but not non-existent

laur89 added 2 commits April 23, 2025 19:44
- package name to grep should be interpreted as a fixed string,
  not as regex. the danger for collision is small, but not non-existent
@oSumAtrIX oSumAtrIX changed the title fix: MOUNT_GREP to grep by fixed string fix: Interpret package name as a string instead of Regex when using grep May 2, 2025
@oSumAtrIX oSumAtrIX merged commit 254f36d into ReVanced:dev May 2, 2025
Copy link

welcome bot commented May 2, 2025

Thank you for contributing to ReVanced. Join us on Discord to receive a role for your contribution.

github-actions bot pushed a commit that referenced this pull request May 2, 2025
## [3.1.1-dev.1](v3.1.0...v3.1.1-dev.1) (2025-05-02)

### Bug Fixes

* Interpret package name as a string instead of Regex when using grep  ([#68](#68)) ([254f36d](254f36d))
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.

2 participants