The GitHub Actions job "Required Checks" on 
texera.git/gh-readonly-queue/release/v1.3/pr-8619-1e56e55fff20a2ef7f60be46dcf3f6c9cb150daf
 has succeeded.
Run started by GitHub user mengw15 (triggered by mengw15).

Head commit for run:
fa0d7ee53079e8ae92c5168779156c513a341ad0 / Meng Wang <[email protected]>
fix(frontend, v1.3): remove the clear button from the dataset version picker 
(#8619)

### What changes were proposed in this PR?

Backport of #8343 to `release/v1.3`: a clean cherry-pick of its squash
commit, no adaptations — the backport commit reuses the squash message
and author, as the automated fast path would. See #8343 for the change
itself (the version dropdown's `nzAllowClear` emitted `null` into a
handler typed `DatasetVersion`, throwing an uncaught `TypeError` and
leaving the page half-cleared).

Opened manually by the v1.3 release manager: the automated fast path
cherry-picked this cleanly and then pushed it straight to
`release/v1.3`, where the Merge Queue ruleset rejected the push
(`GH013`, [run
33705892851](https://github.com/apache/texera/actions/runs/33705892851)).
The Actions-app bypass meant to unblock that path (#8379) was never
created — asfyaml rejects an `Integration` bypass actor — and the
failing job's notification 403s for want of `pull-requests: write`, so
the loss left neither a backport PR nor a comment on #8343. See #8377.

Source: 83e71c2a598451b9e046fdb867a33ab5a8779152

### Any related issues, documentation, discussions?

Backport of #8343. Originally linked #8342.

### How was this PR tested?

The change is identical to #8343, which carries the specs
(`dataset-detail.component.spec.ts`); the backport tree is verified
byte-identical to cherry-picking the squash commit onto `release/v1.3`,
and release-branch CI runs the full matrix on this PR.

### Was this PR authored or co-authored using generative AI tooling?

Yes. Generated-by: Claude Code (claude-opus-5)

Co-authored-by: Tanishq Gandhi 
<[email protected]>

Report URL: https://github.com/apache/texera/actions/runs/35649136910

With regards,
GitHub Actions via GitBox

Reply via email to