Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding a workflow for provider releases with RC version configurations.
These changes are implemented based on the discussion: #5 (comment)
For provider RC releases, the workflow will reference files located in dev/airflow/providers/pypi-rc.
For final release versions, it will use files from dev/airflow/providers.
Currently, workflows are configured for both provider package releases and Airflow package releases.
Each workflow requires a configuration file to determine the necessary validations. This file is generally referred to as the release config file.
In this instance, for providers, two configuration files have been created:
providers-rc-config.yml
providers-pypi-config.yml
There are no strict naming conventions for these configuration files, but their names must be specified as inputs to the workflows.
it looks many file changes happen, due to pre-commit config it refactored some of the files formatting issues :) sorry.