-
Notifications
You must be signed in to change notification settings - Fork 15.9k
Correct version added for new Namespaced log levels feature #55990
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
Merged
ashb
merged 1 commit into
apache:main
from
astronomer:loglevels-namespace-right-release
Sep 24, 2025
Merged
Correct version added for new Namespaced log levels feature #55990
ashb
merged 1 commit into
apache:main
from
astronomer:loglevels-namespace-right-release
Sep 24, 2025
Conversation
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
eladkal
approved these changes
Sep 23, 2025
The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
e2020a0 to
f6fe97f
Compare
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Sep 30, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 1, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 2, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 3, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 4, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 5, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 5, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 7, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 8, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 9, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 10, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 11, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 12, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
dabla
pushed a commit
to dabla/airflow
that referenced
this pull request
Oct 12, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 14, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 15, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 17, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 19, 2025
…5990) The PR that added this was opened before 3.1.0rc, but it didn't get merged until after the branch point, so given it's a new feature, not a bug fix, this won't be released until 3.2.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:ConfigTemplates
changelog:skip
Changes that should be skipped from the changelog (CI, tests, etc..)
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.
The PR that added this was opened before 3.1.0rc, but it didn't get merged
until after the branch point, so given it's a new feature, not a bug fix, this
won't be released until 3.2.0
Noticed by Elad here #55850 (comment)
^ 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 airflow-core/newsfragments.