Nathaniel van Diepen
Nathaniel van Diepen
@jilyaluk poke, any chance you've had time to continue working on this?
@jilyaluk poke again?
What I've discovered so far: - v1.x and v2.x branches are where the work is actually done - PRs from forks fail to build until they've been merged. Use branches...
It looks like new images are published as a new package, but it's private by default and needs to be changed to public.
You will also need to update CHANGELOG.md in the `main` branch when a new release tag has been created.
Creating a new `v#.x` branch requires updating the readme in the `main` branch with the latest information.
I'd be happy to accept a PR to add this to 3.x (and 4.x when it's done). I don't think any of us will get to it for a while...
@pgaskin Due to licensing you'll need to have a device to get the binaries.
I'm sure they are, just not entirely sure where to look. The code that handles updating can be found here: https://github.com/reMarkable/update_engine