changes (#8169)

CHANGES.md

@@ -1,5 +1,35 @@
 # Changelog
 
+# 0.14.18
+
+### New
+
+* Metadata can now be added to jobs (via the `metadata` parameter) and viewed in dagit. You can use it to track code owners, link to docs, or add other useful information.
+* In the Dagit launchpad, the panel below the config editor now shows more detailed information about the state of the config, including error state and whether the config requires further scaffolding or the removal of extra config.
+* FileCache is now marked for deprecation in 0.15.0.
+* In Dagit, the asset catalog now shows the last materialization for each asset and links to the latest run.
+* Assets can now have a `config_schema`. If you attempt to materialize an asset with a config schema in Dagit, you'll be able to enter the required config via a modal.
+
+### Bugfixes
+
+* [helm] Fixed an issue where string floats and integers were not properly templated as image tags.
+* [dagster-k8s] Fixed an issue when using the `k8s_job_executor` where ops with long names sometimes failed to create a pod due to a validation error with the label names automatically generated by Dagster. 
+* [dagster-aws] Fixed an issue where ECS tasks with large container contexts would sometimes fail to launch because their request to the ECS RunTask API was too large.
+
+### Breaking Changes
+
+* `fs_asset_io_manager` has been removed in favor of merging its functionality with `fs_io_manager`. `fs_io_manager` is now the default IO manager for asset jobs, and will store asset outputs in a directory named with the asset key.
+
+### Community Contributions
+
+* Fixed a bug that broke the `k8s_job_executor`’s `max_conccurent` configuration. Thanks @fahadkh!
+* Fixed a bug that caused the `fs_io_manager` to incorrectly handle assets associated with upstream assets. Thanks @aroig!
+
+### Documentation
+
+* [helm] Add documentation for code server image pull secrets in the main chart.
+* The Dagster README has been revamped with documentation and community links.
+
 # 0.14.17
 
 ### New