Closed pdmthorsrud closed 3 years ago
Thinking about it, this might actually be more suitable to include when we have our next release, just so that it can be tested at the same time. WDYT?
Thinking about it, this might actually be more suitable to include when we have our next release, just so that it can be tested at the same time. WDYT?
I guess it will be tested soon enough in hive. Also, the next release for Postgres is scheduled at 27.11.
But, to be clear. There is no difference in the release? The only thing you have done is to include another package to do the same job, right?
Thinking about it, this might actually be more suitable to include when we have our next release, just so that it can be tested at the same time. WDYT?
I guess it will be tested soon enough. The next release is scheduled at 27.11 ;)
But, to be clear. There is no difference in the release? The only thing you have done is to include another package to do the same job, right?
Yep, correct. The only difference is how we get the next_version tag, which now uses a new action. And that action formats it a little different, so I split it to get the correct format :+1:
Closes/fixes/resolves issue(s)?
What was added/changed/fixed?
Related issue(s)? [Optional]
Others [Optional]
Checklist (after created PR)