gopidesupavan commented on code in PR #5: URL: https://github.com/apache/airflow-publish/pull/5#discussion_r1884334778
########## 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: Should we keep separate workflows for rc and final release? Here the `release-type` defines the which packages to consider for final version of packages. When setting `RC_VERSION`, it references the dev SVN folder. and releases packages from here When setting `PYPI_VERSION`, it uses the release SVN folder and compares it against the dev SVN folder. Only packages that match are published to PyPI. The matching logic is for an additional condition where the release manager may have excluded some packages after the voting process. https://github.com/apache/airflow/issues/41937#issuecomment-2507724501 :) -- 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]
