Closed Jobsby closed 1 year ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/185647092
The labels on this github issue will be updated when the story is started.
I wonder why we have only the blobs added. Usually, a postgresql version update have to add the new packages and define the current version like in the pr for the last update.
I'll clarify that internally. Maybe there is a way to just open a PR.
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/185664214
The labels on this github issue will be updated when the story is started.
Find a way without this PR to test the final release. I will close this PR and will test the new release the next day and create a final PR.
The postgresql version 13.11 and 15.3 blobs uploaded to the official S3 blob store. This PR included this two postgresql versions in the blobs.yml. We need this to check and create a new release V.45.