OpenFn / OpenFn/lightning

Update GH Sync actions and migrate connected repos

Open
#4,548 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

sync v2
Dominant language
Elixir
Stars
296
Forks
86
Avg merge
1d 13h
Merged PRs (30d)
50

Description

The two GH sync actions (pull and deploy) need updating to use node 24 (which is the latest LTS)

This itself should be trivial - just bump the node version in the actions. Some other actions probably ought to be updated too.

We also need to change the in-repo actions so that they're not locked to a fix point release. Maybe bind to a minor, so that we can rollout fixes like this and auto-migrate.

The hardest bit is that that any connected repos will need a commit to update the local action to use the latest action version.

TODO list:

  • Update node version on pull action
  • Update node version on deploy action
  • When generating actions for the repos, bind to the latest major version (not a fix point release)
  • Verify that new actions work in a new release
  • Manually migrate repos connected to all managed deployments - https://github.com/OpenFn/lightning/issues/4550
  • Contact admins about any other repos (maybe we hand this off to services?)

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 reviewing the GH sync pull and deploy actions and the action-generation path that binds connected repositories to an action version. Use issue #4550 to identify managed deployments, then migrate the connected repositories and contact administrators about any remaining repositories. Done means all applicable repositories use the updated action version and outstanding owners are contacted.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, devops
Issue type
Refactor
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.