Having spent a while doing patch and update management for critical
infrastructure, I think exposing it directly in the Change Log is the best
possible solution. I'll make sure to let the team know that we can look out
for future issues with some creative use of GitHub search but more
visibility is
Hi Chris,
As Bryce pointed out the current process is managed with the manual
addition of the `Breaking change` label in GitHub. In general after
the Release there is a review process to tag some of those that were
missing.
Currently you could use the GitHub issue search. For example for
13.0.0 a
It's 9:10pm and I should probably check in with my dev team before tossing
this off but I'm trying to give them the longest Thanksgiving break I can.
I'm fairly sure it was this PR: https://github.com/apache/arrow/pull/35656
Long story short, we didn't know it at the time but we were depending on
Hi Chris, this is very much the place to ask a question like this and
thanks for doing so.
Could we get a little more information on the specific change you were
affected by just so we're all on the same page? Was this the bump from
Parquet 2.4 to 2.6 [1] that happened in the PyArrow 13 release [2
Hello,
Le 21/11/2023 à 22:59, Chris Thomas a écrit :
I apologize if this is not the appropriate venue for this request; if
that's the case, please let me know where I should be asking:
Earlier this month Dependabot flagged a security vulnerability with PyArrow
which prompted us to do an upgr
Evening folks,
I apologize if this is not the appropriate venue for this request; if
that's the case, please let me know where I should be asking:
Earlier this month Dependabot flagged a security vulnerability with PyArrow
which prompted us to do an upgrade from v10 to v14.1 of the software.
Obvi
