github-actions[bot] commented on PR #21803:
URL: https://github.com/apache/datafusion/pull/21803#issuecomment-4384913478

   <!-- semver-check-comment -->
   Thank you for opening this pull request!
   
   Reviewer note: 
[cargo-semver-checks](https://github.com/obi1kenobi/cargo-semver-checks) 
reported the current version number is not SemVer-compatible with the changes 
in this pull request (compared against the base branch).
   
   <details>
   <summary>Details</summary>
   
   ```
        Cloning apache/main
       Building datafusion-execution v53.1.0 (current)
          Built [  30.334s] (current)
        Parsing datafusion-execution v53.1.0 (current)
         Parsed [   0.027s] (current)
       Building datafusion-execution v53.1.0 (baseline)
          Built [  30.003s] (baseline)
        Parsing datafusion-execution v53.1.0 (baseline)
         Parsed [   0.027s] (baseline)
       Checking datafusion-execution v53.1.0 -> v53.1.0 (no change; assume 
patch)
        Checked [   0.313s] 222 checks: 221 pass, 1 fail, 0 warn, 30 skip
   
   --- failure trait_added_supertrait: non-sealed trait added new supertraits 
---
   
   Description:
   A non-sealed trait added one or more supertraits, which breaks downstream 
implementations of the trait
           ref: 
https://doc.rust-lang.org/cargo/reference/semver.html#generic-bounds-tighten
          impl: 
https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.47.0/src/lints/trait_added_supertrait.ron
   
   Failed in:
     trait datafusion_execution::memory_pool::MemoryPool gained Any in file 
/home/runner/work/datafusion/datafusion/datafusion/execution/src/memory_pool/mod.rs:186
   
        Summary semver requires new major version: 1 major and 0 minor checks 
failed
       Finished [  62.535s] datafusion-execution
   ```
   
   </details>
   <!-- semver-check-comment -->


-- 
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