Repository automatic dependency upgrades (dependabot)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 215
- Avg merge
- 2h 9m
- Merged PRs (30d)
- 27
Description
Routinely update the dependencies used in the Wing project (such as dependencies of the compiler or of the SDK).
Rationale: newer versions of dependencies often come with performance improvements or security patches, and updating them is less time consuming when they are updated routinely, instead of every 3-6 months. In addition, if we become aware of security vulnerabilities that could affect Wing users because of use of a particular dependency, it is typically easier to apply security patches when our packages are up to date.
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
Start by locating the dependency manifests used by the compiler and SDK, then review how dependency updates are currently handled. Define a routine upgrade process and verify that the project still builds and its existing checks pass after updates are applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, typescript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100