Invalidate output when upgrading Skip
Open
Nobody has claimed this yet.
enhancement
project
- Dominant language
- Swift
- Stars
- 3.2k
- Forks
- 106
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 1
Description
From time to time, people write in with weird Skip issues that go away when they nuke DerivedData and reset package caches, especially when upgrading Skip.
Skip should deposit a version marker in the output folder; if it doesn't match the current version of Skip, Skip should delete its output at the start of the build.
Contributor guide
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
No file or test is named. Trace the build entry point that creates Skip's output, then determine where the current Skip version can be recorded and compared; done means mismatched output is removed at the start of an upgrade build and matching output is retained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100