renovate-bot opened a new pull request, #239:
URL: https://github.com/apache/superset-kubernetes-operator/pull/239

   This PR contains the following updates:
   
   | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | 
[Confidence](https://docs.renovatebot.com/merge-confidence/) |
   |---|---|---|---|
   | [backrefs](https://redirect.github.com/facelessuser/backrefs) | `==7.0` → 
`==8.0` | 
![age](https://developer.mend.io/api/mc/badges/age/pypi/backrefs/8.0?slim=true) 
| 
![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/backrefs/7.0/8.0?slim=true)
 |
   
   ---
   
   ### Release Notes
   
   <details>
   <summary>facelessuser/backrefs (backrefs)</summary>
   
   ### 
[`v8.0`](https://redirect.github.com/facelessuser/backrefs/releases/tag/8.0)
   
   [Compare 
Source](https://redirect.github.com/facelessuser/backrefs/compare/7.0...8.0)
   
   #### 8.0
   
   - **NEW**: Backrefs will preemptively fail, raising a `PatternError`, if 
parsing and finding an unterminated character
     set (`[]`) or an unterminated subpattern (`()`). Both `re` and `regex` 
already do this (`re` just issues a warning
     on Python 3.10), but `backrefs` will now terminate parsing early instead 
of waiting for the underlying regular
     expression parsers to catch it after the fact. This will occur even on 
Python 3.10. If Python 3.10 behavior is
     required, please use Backrefs `7.0` until migration is possible.
   - **NEW**: Backrefs will now raise a `PatternError` in `bre` if global flag 
syntax is not used at the start of the
     pattern. Python `re` already does this, except on Python 3.10 where a 
warning is raised. Backrefs will now do this
     in `bre`, even on Python 3.10, to prevent backtracking in Backrefs' parser 
when global flags are redefined. If the
     old behavior is required, please use `7.0` until migration is possible.
   - **NEW**: Backrefs will now raise a `PatternError` in `bregex` if a global 
flag is not used at the start of the
     pattern. This does not affect inline flags that use the global syntax 
(e.g. `(?i)`) as `regex` allows this to be
     scoped to subpatterns (`(...)`) and affects the pattern after its 
insertion whether in a subpattern or outside a
     subpattern. While regex doesn't specifically restrict global flag 
insertion, only the last instance takes effect,
     Backrefs requires these global flags to be declared at the beginning of 
the pattern to prevent backtracking when
     parsing the pattern. If the old behavior is required, please use `7.0` 
until migration is possible.
   - **NEW**: Various `ValueError` and `SyntaxError` that used to be raised by 
the `bre` or `bregex` parser are now
     raised as `backrefs.util.PatternError`.
   - **FIX**: Fixes in `bregex` related to `regex` handling of inline flags 
using global syntax.
   
   </details>
   
   ---
   
   ### Configuration
   
   📅 **Schedule**: (UTC)
   
   - 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.
   
   ---
   
    - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this 
box
   
   ---
   
   This PR was generated by [Mend Renovate](https://mend.io/renovate/). View 
the [repository job 
log](https://developer.mend.io/github/apache/superset-kubernetes-operator).
   
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yODAuMCIsInVwZGF0ZWRJblZlciI6IjQzLjI4MC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to