Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove duplicated entries in changelog #19331

Merged

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented Oct 30, 2021

Amazon provider had wrong tag set (2.3.0 pointed to rc1 instead
of rc2) which resulted in duplicated entries in changelog.

This PR fixes it


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.

Amazon provider had wrong tag set (2.3.0 pointed to rc1 instead
of rc2) which resulted in duplicated entries in changelog.

This PR fixes it
@potiuk
Copy link
Member Author

potiuk commented Oct 30, 2021

cc: @codenamestif

@potiuk
Copy link
Member Author

potiuk commented Oct 30, 2021

Rerlated to #19328

@github-actions
Copy link

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

@github-actions github-actions bot added the okay to merge It's ok to merge this PR as it does not require more tests label Oct 30, 2021
@potiuk potiuk merged commit 1600f1d into apache:main Oct 30, 2021
@potiuk potiuk deleted the fix-duplicated-entries-in-amazon-changelog branch October 30, 2021 18:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:providers okay to merge It's ok to merge this PR as it does not require more tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants