Skip to content

chore(dagster): release 1.7.0#189

Merged
hugocorreia90 merged 1 commit intomainfrom
chore/dagster-release-1.7.0
Apr 20, 2026
Merged

chore(dagster): release 1.7.0#189
hugocorreia90 merged 1 commit intomainfrom
chore/dagster-release-1.7.0

Conversation

@hugocorreia90
Copy link
Copy Markdown
Contributor

Tracks engine 1.11.0. Pydantic bindings for the trust-system arcs (Arcs 1–7 first waves + Arc 6 wave 2 + Arc 7 wave 2 wave-1).

Summary

  • Arc 1BranchOutput, BranchListOutput, BranchDeleteOutput, ReplayOutput, ColumnLineageOutput.direction
  • Arc 2RunOutput.cost_summary, per-materialization cost_usd, BudgetConfig, budget_breach event
  • Arc 3circuit_breaker_tripped / _recovered event variants
  • Arc 4TraceOutput / TraceLane / TraceMaterialization
  • Arc 5AiGenerateOutput.models
  • Arc 6 wave 2PortabilityConfig on RockyProject (lowercase Dialect enum)

P001 / P002 lint diagnostics (Arcs 6 wave 1 + 7 wave 1) flow through the existing Diagnostic shape — no new Pydantic models needed.

The bindings themselves were regenerated incrementally as each engine PR landed (gated by codegen-drift.yml CI). This PR is purely the version bump + changelog narrative.

Test plan

  • pyproject.toml bumped 1.6.0 → 1.7.0
  • CI green on this PR
  • After engine 1.11.0 + this PR merge: tag dagster-v1.7.0 on the merged commit and push to trigger dagster-release.yml (publishes wheel + PyPI via OIDC)

Tracks engine 1.11.0. Pydantic bindings for the trust-system arcs
(Arcs 1-7 first waves + Arc 6 wave 2 + Arc 7 wave 2 wave-1).

The bindings were regenerated incrementally as each engine PR landed
via `just codegen` and gated by `codegen-drift.yml` CI; this PR is
purely the version bump + changelog narrative for the cumulative
release. No code changes beyond pyproject.toml and CHANGELOG.md.

Arc 6 wave 1 (P001) and Arc 7 wave 1 (P002) flow through the existing
Diagnostic shape — no new Pydantic models needed.
@hugocorreia90 hugocorreia90 merged commit 9f9e1ca into main Apr 20, 2026
8 checks passed
@hugocorreia90 hugocorreia90 deleted the chore/dagster-release-1.7.0 branch April 20, 2026 17:15
hugocorreia90 added a commit that referenced this pull request Apr 20, 2026
The fixture version strings and the dagster-rocky wheel-version in
uv.lock still reflected engine-v1.10.0 / dagster-v1.6.0 from before the
coordinated 1.11.0 / 1.7.0 release (PRs #188, #189). Regenerated via
`just regen-fixtures` and `just codegen`; the 35 fixture diffs are
pure `version` string bumps with no shape changes.

Unblocks the codegen-drift CI check on PR #194.
hugocorreia90 added a commit that referenced this pull request Apr 20, 2026
…tioning (#194)

* docs: align READMEs, llms.txt, and agent files with trust-system positioning

- engine/README.md: lead with trust-system framing; add ELT scope table,
  seven trust dimensions section, and Branches / Cost / Observability /
  Portability rows in the features table.
- README.md (monorepo root): one-liner now leads with "trust system for
  your data" + "Keep Databricks or Snowflake, bring Rocky for the DAG."
- docs/public/llms.txt: replace the "owns the T" positioning and add
  explicit ELT scope bullets so LLM-crawlers pick up the accurate
  coverage (rocky load, bronze replication).
- CLAUDE.md (root), engine/AGENTS.md: one-line wording fixes so future
  agent guidance doesn't carry the stale "replaces dbt" frame.

All changes are pure copy; no code or feature changes. Docs build still
passes (69 pages, 1.68s).

* chore(dagster): refresh generated fixtures + uv.lock for engine-v1.11.0

The fixture version strings and the dagster-rocky wheel-version in
uv.lock still reflected engine-v1.10.0 / dagster-v1.6.0 from before the
coordinated 1.11.0 / 1.7.0 release (PRs #188, #189). Regenerated via
`just regen-fixtures` and `just codegen`; the 35 fixture diffs are
pure `version` string bumps with no shape changes.

Unblocks the codegen-drift CI check on PR #194.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant