This is an automated email from the ASF dual-hosted git repository.
kaxilnaik pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new d9da04d274e Remove old (3.0) newsfragments (#51661)
d9da04d274e is described below
commit d9da04d274e2ace4451c1bc643069083915da334
Author: Kaxil Naik <[email protected]>
AuthorDate: Thu Jun 12 22:25:09 2025 +0530
Remove old (3.0) newsfragments (#51661)
This were missed when newsfragments were cleared after 3.0.0 release.
---
airflow-core/newsfragments/43975.significant.rst | 25 --------
airflow-core/newsfragments/aip-66.significant.rst | 75 -----------------------
2 files changed, 100 deletions(-)
diff --git a/airflow-core/newsfragments/43975.significant.rst
b/airflow-core/newsfragments/43975.significant.rst
deleted file mode 100644
index dd8e4c02685..00000000000
--- a/airflow-core/newsfragments/43975.significant.rst
+++ /dev/null
@@ -1,25 +0,0 @@
-Timer and timing metrics are now standardized to milliseconds
-
-In Airflow 3.0, the ``timer_unit_consistency`` setting in the ``metrics``
section is removed as it is now the default behaviour.
-This is done to standardize all timer and timing metrics to milliseconds
across all metric loggers.
-
-Airflow 2.11 introduced the ``timer_unit_consistency`` setting in the
``metrics`` section of the configuration file. The
-default value was ``False`` which meant that the timer and timing metrics were
logged in seconds. This was done to maintain
-backwards compatibility with the previous versions of Airflow.
-
-* Types of change
-
- * [ ] Dag changes
- * [x] Config changes
- * [ ] API changes
- * [ ] CLI changes
- * [ ] Behaviour changes
- * [ ] Plugin changes
- * [ ] Dependency changes
- * [ ] Code interface changes
-
-* Migration rules needed
-
- * ``airflow config lint``
-
- * [x] ``metrics.timer_unit_consistency``
diff --git a/airflow-core/newsfragments/aip-66.significant.rst
b/airflow-core/newsfragments/aip-66.significant.rst
deleted file mode 100644
index 3885b073b0d..00000000000
--- a/airflow-core/newsfragments/aip-66.significant.rst
+++ /dev/null
@@ -1,75 +0,0 @@
-Support DAG versioning by introducing DAG Bundles
-
-The following DAG parsing configuration options were moved into the
``dag_processor`` section:
-
-* ``[core] dag_file_processor_timeout`` → ``[dag_processor]
dag_file_processor_timeout``
-* ``[scheduler] parsing_processes`` → ``[dag_processor] parsing_processes``
-* ``[scheduler] file_parsing_sort_mode`` → ``[dag_processor]
file_parsing_sort_mode``
-* ``[scheduler] max_callbacks_per_loop`` → ``[dag_processor]
max_callbacks_per_loop``
-* ``[scheduler] min_file_process_interval`` → ``[dag_processor]
min_file_process_interval``
-* ``[scheduler] stale_dag_threshold`` → ``[dag_processor] stale_dag_threshold``
-* ``[scheduler] print_stats_interval`` → ``[dag_processor]
print_stats_interval``
-
-The following DAG parsing configuration options were moved into the
``logging`` section:
-
-* ``[scheduler] child_process_log_directory`` → ``[logging]
dag_processor_child_process_log_directory``
-
-The default value of ``[logging] dag_processor_child_process_log_directory``
was changed from
-``AIRFLOW_HOME/logs/scheduler`` to ``AIRFLOW_HOME/logs/dag-processor``, which
moves the parsing logs for dag files into
-that new location.
-
-The "subdir" concept has been superseded by the "bundle" concept. Users are
able to
-define separate bundles for different DAG folders, and can refer to them by
the bundle name
-instead of their location on disk.
-
-The ``-subdir`` option of the following commands has been replaced with
``--bundle-name``:
-
-* ``airflow dag-processor``
-* ``airflow dags list-import-errors``
-* ``airflow dags report``
-
-The ``--subdir`` option has been removed from the following commands:
-
-* ``airflow dags next-execution``
-* ``airflow dags pause``
-* ``airflow dags show``
-* ``airflow dags show-dependencies``
-* ``airflow dags state``
-* ``airflow dags test``
-* ``airflow dags trigger``
-* ``airflow dags unpause``
-
-Dag bundles are not initialized in the triggerer. In practice, this means that
triggers cannot come from a dag bundle.
-This is because the triggerer does not deal with changes in trigger code over
time, as everything happens in the main process.
-Triggers can come from anywhere else on ``sys.path`` instead.
-
-.. Provide additional contextual information
-
-.. Check the type of change that applies to this change
-
-* Types of change
-
- * [ ] Dag changes
- * [x] Config changes
- * [ ] API changes
- * [x] CLI changes
- * [ ] Behaviour changes
- * [ ] Plugin changes
- * [ ] Dependency changes
- * [ ] Code interface changes
-
-.. List the migration rules needed for this change (see
https://github.com/apache/airflow/issues/41641)
-
-* Migration rules needed
-
- * ``airflow config lint``
-
- * [x] ``[core] dag_file_processor_timeout`` → ``[dag_processor]
dag_file_processor_timeout``
- * [x] ``[scheduler] parsing_processes`` → ``[dag_processor]
parsing_processes``
- * [x] ``[scheduler] file_parsing_sort_mode`` → ``[dag_processor]
file_parsing_sort_mode``
- * [x] ``[scheduler] max_callbacks_per_loop`` → ``[dag_processor]
max_callbacks_per_loop``
- * [x] ``[scheduler] min_file_process_interval`` → ``[dag_processor]
min_file_process_interval``
- * [x] ``[scheduler] stale_dag_threshold`` → ``[dag_processor]
stale_dag_threshold``
- * [x] ``[scheduler] print_stats_interval`` → ``[dag_processor]
print_stats_interval``
- * [x] ``[scheduler] dag_dir_list_interval`` → ``[dag_processor]
refresh_interval``
- * [x] ``[scheduler] dag_dir_list_interval`` → ``[logging]
dag_processor_child_process_log_directory``
