LivelyKernel / LivelyKernel/livelykernel-scripts.app
Keeping app dependencies up-to-date
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
from @mroeder
Today I wanted to work with the WebResource/Proxy in my local installation and I found it not working (live_star). So I spent some time fixing it so that it does the job now, but when I though it would be a good idea to checkin those changes, I saw that the life_star has change since it was included in the app package (and also some fixes have already been applied). The version in the Lively Kernel Scripts App still is 0.0.3 while the current version on github is 0.1.2.
Suggestion: Update the package with the most recent (and stable?) version of life_star. And maybe have a look at the other dependencies as well and update them.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the app package metadata that records the life_star dependency and compare its 0.0.3 version with the current GitHub release mentioned in the issue. Check how WebResource/Proxy behaves with the updated package, then review the other declared dependencies. Done means the app uses the latest stable compatible versions and the affected functionality still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- objective-c
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100