planetscale / planetscale/database-js
CI for tagging and pushing releases
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Right now, our release process is manual and a bit flawed.
Our internal steps have been:
npm version minor
git push --tags
npm publish
But this isn't great.
- it relies on being able to bypass branch protections and push directly to main. The "bump" commit goes directly to
main. https://github.com/planetscale/database-js/commit/68ed111f7f810a0e8eaae961e6d0ed77de4d593e This requires permission or rules to bypass branch protection. npm publishrequires permission to push tonpm, and this should just be a bot.
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 reviewing the repository's current release process against the documented npm version minor, git push --tags, and npm publish steps. Define the CI workflow and permissions needed so tagging and npm publishing no longer require manual pushes or personal credentials; done means releases can be performed by the bot without bypassing branch protection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100