Skip to content

[CHORE] Ensure tool versions get saved as artifacts available to the rendered charts #10

@darcyclarke

Description

@darcyclarke

📋 Description

Currently, the tooling versions will get logged in the workflow run but those logs are ephemeral & the charts are intended to save the data/state overtime (so its important to store the versions of the tools we've benchmarked as they'll change over time).

📂 Category

Tooling Improvements - Improve developer tools

🎯 Motivation

Clarity & explicteness of which version of a tool was benchmarked

🎌 Scope of Work

.github/workflows/benchmark.yaml & scripts/generate-chart.js

📊 Impact Level

Medium - Noticeable improvements, minimal risk

⏰ Urgency

Medium - Should be done in next sprint

⚠️ Breaking Changes

No response

🧪 Testing Strategy

No response

✅ Definition of Done

  • Changes implemented as described
  • Existing functionality verified unaffected
  • Tests updated and passing
  • Documentation updated if needed
  • Code reviewed and approved
  • Performance impact assessed
  • Breaking changes documented
  • Migration guide provided (if applicable)
  • Rollback plan prepared (if high risk)

🔗 Dependencies

No response

⏱️ Estimated Timeline

No response

📎 Additional Context

No response

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions