Create the change log and migration guide for 1.10 (#27715)

CHANGES.md

@@ -1,5 +1,68 @@
 # Changelog
 
+## 1.10.0 (core) / 0.26.0 (libraries)
+
+### New
+
+- Added a new `AutomationCondition.data_version_changed()` condition.
+- [dagster-msteams] Added support for sending messages to PowerAutomate flows using AdaptiveCard formatting.
+- `dagster definitions validate` is now less verbose, primarily highlighting load errors.
+- [ui] Made defunct code locations removable when editing environment variables.
+- [ui] Added a warning icon to the Agents item in Deployment settings, indicating when there are no active agents.
+- [dagster-tableau] Changed logic to show embedded data sources in case published data sources are not present. Also, pulled more metadata from Tableau. (Thanks [@VenkyRules](https://github.com/VenkyRules)!)
+- Added new decorators to reflect our [new API lifecycle](https://docs.dagster.io/api/api-lifecycle): `@preview`, `@beta` and `@superseded`. Also added new annotations and warnings to match these new decorators.
+
+### Bugfixes
+
+- [ui] Fixed persistence of the group-by setting in the run timeline view.
+- [ui] Fixed timestamped links to asset pages from asset check evaluations in run logs.
+- [ui] Fixed excessive rendering and querying on the Concurrency configuration page.
+- Fixed the step stats calculations for steps that fail and request a retry before the step starts. This happened if a failure occurred in the step worker before the compute function began execution. This should help with sporadic hanging of step retries.
+- Fixed an issue where the Concurrency UI was broken for keys with slashes.
+- Fixed an issue with emitting `AssetResult` with ops or multi-assets that are triggered multiple times in the same run.
+- [dagster-dbt] Fixed a bug introduced in dagster-dbt 0.25.7 that would cause execution to fail when using the `@dbt_assets` decorator with an `io_manager_key` specified.
+- [dagster-dbt] Refactored `UnitTestDefinition` instantiation to address failure to initialize dbt models with unit tests. (Thanks [@kang8](https://github.com/kang8)!)
+- Fixed issue where `dagster instance migrate` was failing for instances with tables having non-empty concurrency limits.
+- Fixed an issue where Declarative Automation sensors in code locations that included source assets referencing assets with automation conditions in other code locations would sometimes cause duplicate runs to be created.
+- Turned on run blocking for concurrency keys/pools by default. For op granularity, runs are dequeued if there exists at least one op that can execute once the run has started. For run granularity, runs are dequeued if all pools have available slots.
+- [dagster-dbt] Added pool support.
+- [dagster-dlt] Added pool support.
+- [dagster-sling] Added pool support.
+
+### Documentation
+
+- Corrected docs on managing concurrency.
+- Fixed a Markdown link to "assets metadata." (Thanks [@rchrand](https://github.com/rchrand)!)
+- Fixed a `pip install` command for Zsh. (Thanks [@aimeecodes](https://github.com/aimeecodes)!)
+
+### Breaking Changes
+
+- The `include_sources` param on all `AssetSelection` APIs has been renamed to `include_external_assets`.
+- Disallowed invalid characters (i.e. anything other than letters, numbers, dashes, and underscores) in pool names.
+- Changed the default run coordinator to be the queued run coordinator. This requires the Dagster daemon to be running for runs to be launched. To restore the previous behavior, you can add the following configuration block to your `dagster.yaml`:
+
+  ```
+  run_coordinator:
+    module: dagster.core.run_coordinator.sync_in_memory_run_coordinator
+    class: SyncInMemoryRunCoordinator
+  ```
+
+### Deprecations
+
+- [dagster-sdf] Moved the `dagster-sdf` library to the community-supported repo.
+- [dagster-blueprints] Removed the `dagster-blueprints` package. We are actively developing a project, currently named Components, that has similar goals to Blueprints of increasing the accessibility of Dagster.
+- Removed the `@experimental` decorator in favor of the `@preview` and `@beta` decorators. Also removed annotations and warnings related to the `@experimental` decorator.
+
+### Dagster Plus
+
+- Shipped a range of improvements to alerts in Dagster+, including more granular targeting, streamlined UIs, and more helpful content. Stay tuned for some final changes and a full announcement in the coming weeks!
+
+## 1.9.13 (core) / 0.25.13 (libraries)
+
+### Dagster Plus
+
+- Fixed a bug where runs using global op concurrency would raise an exception when claiming a concurrency slot.
+
 ## 1.9.12 (core) / 0.25.12 (libraries)
 
 ### New

MIGRATION.md

@@ -2,23 +2,33 @@
 
 When new releases include breaking changes or deprecations, this document describes how to migrate.
 
+## Migrating to 1.10.0
+
+### Deprecations
+
+- We've refreshed our integrations with popular ELT tools like [Fivetran](https://docs.dagster.io/integrations/libraries/fivetran) and [Airbyte](https://docs.dagster.io/integrations/libraries/airbyte/airbyte-oss) to leverage Dagster's asset-based patterns better and provide enhanced visibility into your data pipelines. The old integration patterns are still available, so there are no breaking changes, but we encourage users to take advantage of the new capabilities!
+
+### Breaking changes
+
+- Pool names now only accept letters, numbers, dashes, and underscores.
+
 ## Migrating to 1.9.0
 
-## Database migration
+### Database migration
 
 - This release includes database schema and data migrations to improve the performance of the Runs page. We highly recommend running these migrations to avoid slow page loads of the new Runs page. The migration will add a new column to the `runs` table, a new column to the `bulk_actions` table and a new `backfill_tags` table. A data migration will populate the new columns and table. Run `dagster instance migrate` to run the schema and data migration.
 
-## Notable behavior changes
+### Notable behavior changes
 
 - Backfills have been moved from their own tab underneath the Overview page to entries within the table on the Runs page. This reflects the fact that backfills and runs are similar entities that share most properties. You can continue to use the legacy Runs page with the “Revert to legacy Runs page” user setting. ([GitHub Discussion](https://github.com/dagster-io/dagster/discussions/24898))
 - By default, `AutomationConditionSensorDefinitions` will now emit backfills to handle cases where more than one partition of an asset is requested on a given tick. This allows that asset's `BackfillPolicy` to be respected. This feature can be disabled by setting `allow_backfills` to `False` on the sensor definition.
 
-## Deprecations
+### Deprecations
 
 - The `DataBricksPysparkStepLauncher`, `EmrPySparkStepLauncher`, and any custom subclass of `StepLauncher` have been marked as deprecated, but will not be removed from the codebase until Dagster 2.0 is released, meaning they will continue to function as they currently do for the foreseeable future. Their functionality has been superseded by the interfaces provided by `dagster-pipes`, and so future development work will be focused there.
 - The experimental `@multi_asset_sensor` has been marked as deprecated, but will not be removed from the codebase until Dagster 2.0 is released, meaning it will continue to function as it currently does for the foreseeable future. Its functionality has been largely superseded by the `AutomationCondition` system.
 
-## Breaking changes
+### Breaking changes
 
 - `dagster` no longer supports Python 3.8, which hit EOL on 2024-10-07.
 - `dagster` now requires `pydantic>=2` .