Skip to content

chore: triage and close resolved issues #694

@andreahlert

Description

@andreahlert

Part of #690

Several open issues had been resolved by merged PRs but were never closed, plus many stale issues accumulated over 2+ years. Full triage completed.

Closed as resolved (PR merged)

Issue Resolved by
#501 (expose current action) PR #506
#416 (override state in initialize_from) PR #632
#523 (expose ENV variables for S3) PR #525
#360 (API for streaming + iterating) PR #532
#413 (OpenTelemetry async error) PR #590
#287 (Hamilton DAG actions in UI) PR #301 (partial)
#635 (add -src to source releases) PR #651 (already closed)
#638 (copyrights in Apache headers) PR #651 + #637 (already closed)
#603 (release scripts for Apache) PRs #595, #599, #604, #609, #625, #628 (already closed)

Closed as superseded

Issue Reason
#113 (Umbrella Phase 2) ~60% done, remaining items tracked individually (#56, #46)
#207 (Langsmith integration) Duplicate of #206

Closed as stale (no activity 12+ months, no PR, no demand)

#10, #14, #33, #46, #116, #205, #244, #268, #300, #305, #341, #395, #441

Full review completed

  • All 76 open issues cross-referenced with merged PRs
  • Issues older than 12 months reviewed for relevance
  • 21 issues closed total in this triage pass

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions