tursodatabase / tursodatabase/libsql-client-ts
Setup changesets for CI
Open
Nobody has claimed this yet.
developer experience
enhancement
good first issue
help wanted
- Dominant language
- TypeScript
- Stars
- 576
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
We should consider adding Changesets so that releases (+ next/beta tags) are automated.
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 reviewing the repository's current CI and release configuration, then read the linked Changesets project documentation. Determine how releases and next/beta tags are currently handled and define the required automation. Done means the release workflow uses Changesets and produces the intended release tags reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100