Add release management command to retreive provider version metadata#32119
Merged
potiuk merged 1 commit intoapache:mainfrom Jun 25, 2023
Merged
Add release management command to retreive provider version metadata#32119potiuk merged 1 commit intoapache:mainfrom
potiuk merged 1 commit intoapache:mainfrom
Conversation
potiuk
requested review from
eladkal,
ephraimbuddy,
hussein-awala,
pierrejeambrun and
utkarsharma2
Member
Author
|
Hey Everyone - this is the next step in building more information about our packages (including SBOM information) - getting historical information about providers which can be easily updated and refrehsed. We will need this one in the next steps, when we will use the information to generate SBOM information for providers, but also to improve provider's CHANGELOG in the future. |
This new command will refresh and store generated provider version metadata - including the time when provider has been released and which airflow version it has been associated with. This information will eventually be used in generating provider's changelogs, and it will be used to generate provider-specific dependencies (we need to know which airflow version provider specific dependencies should be compared with). This is the next step in publishing SBOM information, but it will also be accompanied by updating more information for past releases of the providers.
potiuk
force-pushed
the
add-provider-metadata
branch
from
fc000e7 to
18f2c72
Compare
Member
Author
|
(see https://github.com/apache/airflow/pull/32119/files#diff-546c8884e1520ba1e582bd392f6280d1c15037bd6705efbfbc6fd339de794ec7 - it will show the results that we get from running it). |
Member
Author
|
cc: @eladkal - I will plug it in the release preparation process as one of the next steps. I just want to add one thing at a time. |
utkarsharma2
approved these changes
Jun 25, 2023
ferruzzi
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Jun 27, 2023
…pache#32119) This new command will refresh and store generated provider version metadata - including the time when provider has been released and which airflow version it has been associated with. This information will eventually be used in generating provider's changelogs, and it will be used to generate provider-specific dependencies (we need to know which airflow version provider specific dependencies should be compared with). This is the next step in publishing SBOM information, but it will also be accompanied by updating more information for past releases of the providers.
potiuk
added a commit
that referenced
this pull request
Jul 2, 2023
…32119) This new command will refresh and store generated provider version metadata - including the time when provider has been released and which airflow version it has been associated with. This information will eventually be used in generating provider's changelogs, and it will be used to generate provider-specific dependencies (we need to know which airflow version provider specific dependencies should be compared with). This is the next step in publishing SBOM information, but it will also be accompanied by updating more information for past releases of the providers. (cherry picked from commit 63e1117)
53 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This new command will refresh and store generated provider version metadata - including the time when provider has been released and which airflow version it has been associated with.
This information will eventually be used in generating provider's changelogs, and it will be used to generate provider-specific dependencies (we need to know which airflow version provider specific dependencies should be compared with).
This is the next step in publishing SBOM information, but it will also be accompanied by updating more information for past releases of the providers.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.