additions to the 0.14.15 changelog (#7856)

* changelog 0.14.15

* additions to the 0.14.15 changelog

* add revert explain

Co-authored-by: yuhan <yuhan@elementl.com>

CHANGES.md

@@ -8,6 +8,7 @@
 - Repositories can now contain asset definitions and source assets for the same asset key.
 - `OpExecutionContext` (provided as the `context` argument to Ops) now has fields for, `run`, `job_def`, `job_name`, `op_def`, and `op_config`. These replace `pipeline_run`, `pipeline_def`, etc. (though they are still available).
 - When a job is partitioned using an hourly, daily, weekly, or monthly partitions definition, `OpExecutionContext` now offers a `partition_time_window` attribute, which returns a tuple of datetime objects that mark the bounds of the partition’s time window.
+- `AssetsDefinition.from_graph` now accepts a `partitions_def` argument.
 - [dagster-k8s] Removed an unnecessary `dagster-test-connection` pod from the Dagster Helm chart.
 - [dagster-k8s] The `k8s_job_executor` now polls the event log on a ~1 second interval (previously 0.1). Performance testing showed that this reduced DB load while not significantly impacting run time.
 - [dagit] Removed package pins for `Jinja2` and `nbconvert`.
@@ -20,7 +21,6 @@
 - [dagit] The Asset graph now includes a “Reload definitions” button which reloads your repositories.
 - [dagit] On all DAGs, you can hold shift on the keyboard to switch from mouse wheel / touch pad zooming to panning. This makes it much easier to scroll horizontally at high speed without click-drag-click-drag-click-drag.
 - [dagit] a `--log-level` flag is now available in the dagit cli for controlling the uvicorn log level.
-- [dagster-dbt] Software-defined assets from dbt models now include the schema in the asset key.
 - [dagster-dbt] The `load_assets_from_dbt_project()` and `load_assets_from_dbt_manifest()` utilities now have a `use_build_command` parameter. If this flag is set, when materializing your dbt assets, Dagster will use the `dbt build` command instead of `dbt run`. Any tests run during this process will be represented with AssetObservation events attached to the relevant assets. For more information on `dbt build`, see the [dbt docs](https://docs.getdbt.com/reference/commands/build).
 - [dagster-dbt] If a dbt project successfully runs some models and then fails, AssetMaterializations will now be generated for the successful models.
 - [dagster-snowflake] The new Snowflake IO manager, which you can create using `build_snowflake_io_manager` offers a way to store assets and op outputs in Snowflake. The `PandasSnowflakeTypeHandler` stores Pandas `DataFrame`s in Snowflake.
@@ -38,6 +38,10 @@
 
 - [dagster-aws] `PickledObjectS3IOManager` now uses `list_objects` to check the access permission. Thanks @trevenrawr!
 
+### Breaking Changes
+
+- [dagster-dbt] The asset definitions produced by the experimental `load_assets_from_dbt_project` and `load_assets_from_dbt_manifest` functions now include the schemas of the dbt models in their asset keys. To revert to the old behavior: `dbt_assets = load_assets_from_dbt_project(..., node_info_to_asset_key=lambda node_info: AssetKey(node_info["name"])`.
+
 ### Experimental
 
 - The `TableSchema` API is no longer experimental.