OpenFn / OpenFn/kit

Split up Run Versions and Step Versions (worker)

Open
#574 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
21
Forks
23
Avg merge
1d 22h
Merged PRs (30d)
17

Description

Have “run versions” at the start with something like the below and then “step versions” for each step

Versions for run 4eb3654e-762f-4ee2-83f0-47c1f3b9eea4:
    ▸ node.js                  18.19.0
    ▸ worker                   0.6.0
    ▸ engine                   0.3.0
Versions for step 4eb3654e-762f-4ee2-83f0-47c1f3b9eea5 
    ▸ @openfn/language-http    4.1.1
Log
Log
Log
Versions for step 4eb3654e-762f-4ee2-83f0-47c1f3b9eea6
    ▸ @openfn/language-http    6.0.0
Log
Log
Log

This affects CLI and the Worker

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the CLI and Worker code that currently prints run and step versions together. Compare the existing output with the example in this issue; done means run-level versions appear once before each step's versions and logs, consistently across both CLI and Worker.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend, cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.