potiuk commented on code in PR #5: URL: https://github.com/apache/airflow-publish/pull/5#discussion_r1885593776
########## providers-release-config.yml: ########## @@ -0,0 +1,45 @@ +project: + name: airflow-publish + description: "Publish airflow packages to PyPI" +publisher: + name: airflow + url: https://dist.apache.org/repos/dist/dev/airflow + path: "providers/" +checks: + svn: + - id: extension + description: "Validate svn package extensions" + identifiers: + - type: regex + pattern: ".*(py3-none-any.whl|py3-none-any.whl.asc|py3-none-any.whl.sha512|tar.gz|tar.gz.asc|tar.gz.sha512)$" + + - id: package_name + description: "Validate svn package names" + identifiers: + - type: regex + pattern: ".*(apache_airflow_providers.*)$" + + checksum: + - id: checksum + description: "Validate check sum with SHA512" + algorithm: "sha512" + + signature: + - id: signature + description: "Validate signatures with GPG of packages" + method: gpg + keys: "https://dist.apache.org/repos/dist/release/airflow/KEYS"; + + publish: + id: publish + description: "Publish airflow providers packages to PyPI" + release-type: "RC_VERSION" Review Comment: This should work a BIT differently. 1) We will have to modify the release process https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md to also add PYPI packages to SVN. We do not do it currently - because we do not technically need them in SVN, but with this workflow we will need it. I can draft a proposal there and we can discuss it with @eladkal (and try it out in this week's release process). What I think should happen is that we should have "pypi-rc" sub-folder in providers and `pypi` packages (those with `rc*` in the name should be placed there. 2) Then I think it's best to release RC packages from the the `dev/providers/pypi-rc` and when voting is complete we release "final" packages from "dev/providers" -> NOTE from `dev` not `release` - JUST BEFORE we move them to `release`. This way we will not have to compare anything. This will happen after the packages were removed from "dev/release" by the release manager, and just before we run `svn mv` to move them to release. Which will make it very simple - we upload the same final packages that we move to release. Does it make sense? I will draft a PR where I will explain the process to follow on the release management process so that we can see and comment on it. -- 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]
