Skip to content

chore: release engine-v1.16.0 + dagster-v1.12.0 + vscode-v1.8.0#245

Merged
hugocorreia90 merged 3 commits intomainfrom
chore/release-governance-waveplan
Apr 23, 2026
Merged

chore: release engine-v1.16.0 + dagster-v1.12.0 + vscode-v1.8.0#245
hugocorreia90 merged 3 commits intomainfrom
chore/release-governance-waveplan

Conversation

@hugocorreia90
Copy link
Copy Markdown
Contributor

Summary

Release PR bundling the governance waveplan — five merged PRs that collectively ship column classification + masking, run-record audit trail, a rocky compliance rollup verb, role-graph reconciliation, and data retention policies. Plus three FR-004 / state-path follow-ups that accumulated since v1.15.0.

After this PR merges, tagging engine-v1.16.0 + dagster-v1.12.0 + vscode-v1.8.0 triggers the matching *-release.yml workflows to build + publish.

Version bumps

Artifact From To
engine (20 crates, excl. rocky-bigquery on its own track) 1.15.0 1.16.0
dagster-rocky wheel 1.11.0 1.12.0
Rocky VS Code extension 1.7.0 1.8.0

Bundled PRs

Governance waveplan (engine-v1.16.0)

FR-004 / state-path follow-ups

Test plan

  • cargo test --workspace — green (all 2500+ tests)
  • cargo clippy --workspace --all-targets -- -D warnings — green
  • cargo fmt --check — green (rustfmt 1.95.0)
  • just codegen — idempotent, no drift (CHANGELOGs + version bumps only)
  • After merge: git tag -a engine-v1.16.0 -m "Release engine-v1.16.0" && git push origin engine-v1.16.0 triggers engine-release.yml (5-platform matrix build + GH Release)
  • After merge: git tag -a dagster-v1.12.0 -m "Release dagster-v1.12.0" && git push origin dagster-v1.12.0 triggers dagster-release.yml (PyPI publish via OIDC)
  • After merge: git tag -a vscode-v1.8.0 -m "Release vscode-v1.8.0" && git push origin vscode-v1.8.0 triggers vscode-release.yml (Marketplace publish via VSCE_PAT)

Bundles the governance waveplan — five merged PRs (#240 audit trail,
#241 classification + masking, #242 rocky compliance, #243 role-graph,
#244 retention) on top of three FR-004 / state-path follow-ups
(#237 error-path idempotency, #238 state-path unification,
#239 success-path idempotency finalize).

Version bumps: engine 1.15.0 → 1.16.0, dagster-rocky 1.11.0 → 1.12.0,
vscode extension 1.7.0 → 1.8.0.

CHANGELOGs updated for all three artifacts.
Fixture drift flagged by CI (`codegen-drift.yml`). Fixtures are captured
from the live engine binary — the version-string bump to 1.16.0 ripples
through every `version` field, and the Wave A audit-trail work (#240)
adds the 8 `RunRecord` fields to `rocky history` output, which the
playground POC now emits.

Regenerated via `just regen-fixtures` against
`examples/playground/pocs/00-foundations/00-playground-default`.
Every CLI output's top-level `version` is `env!("CARGO_PKG_VERSION")`
at emit time, so every engine version bump rippled through all 38
captured fixtures — every release PR fought `codegen-drift.yml` until
`just regen-fixtures` was re-run.

Extend the existing `AUDIT_FIELD_SENTINELS` set (Wave A already
sentineled the audit-trail `rocky_version` field + hostname / git
commit / etc.) with the top-level `version` key → `"0.0.0-SENTINEL"`.
After this, version bumps only touch Cargo.toml / pyproject.toml /
package.json / CHANGELOGs — never fixtures.

Regen captured all 38 fixtures; top-level `version` now uniformly
renders as `"0.0.0-SENTINEL"`.
@hugocorreia90 hugocorreia90 merged commit 69d0fdc into main Apr 23, 2026
15 of 16 checks passed
@hugocorreia90 hugocorreia90 deleted the chore/release-governance-waveplan branch April 23, 2026 23:56
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