potiuk commented on issue #19569:
URL: https://github.com/apache/airflow/issues/19569#issuecomment-969972852
And credit for tonight upload goes to @kaxil actually ;)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
potiuk commented on issue #19569:
URL: https://github.com/apache/airflow/issues/19569#issuecomment-969972101
I recommend using 'versioned' images though :). You always have to run
migration when you switch so this should be a conscious effort rather than
accidental upgrade.
--
This is
potiuk commented on issue #19569:
URL: https://github.com/apache/airflow/issues/19569#issuecomment-968093692
Yeah - the solution is really to semi-automate in a smart way. The fix I
came up with in #19573 improves it in the way that it detects whethere we are
(semi-automatically)
potiuk commented on issue #19569:
URL: https://github.com/apache/airflow/issues/19569#issuecomment-968055704
But all the steps of releasing including building packages. Building images
etc. are actually done in GitHub actions basically after every pull request. We
even publish CI mages
potiuk commented on issue #19569:
URL: https://github.com/apache/airflow/issues/19569#issuecomment-968055180
Yep. Releasing via GitHub actions is far too vulnerable to injecting
malicious code
--
This is an automated message from the Apache Git Service.
To respond to the message,
potiuk commented on issue #19569:
URL: https://github.com/apache/airflow/issues/19569#issuecomment-967801638
Ah - actually it WAS there but was not followed (even by mysefl) so I have
to see how we can make it more difficult to skip:
```
If this is the newest image released, push
potiuk commented on issue #19569:
URL: https://github.com/apache/airflow/issues/19569#issuecomment-967800512
Good. Spot. I fixed it now in the repo. I will update the process of
releasing to include refresh of the latest images as it was missing!
--
This is an automated message from the
