Automatically release on a schedule when the release-please PR contains a wat bump
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 5
- Forks
- 1
- Avg merge
- 3m
- Merged PRs (30d)
- 4
Description
Summary
Currently the release-please PR (e.g. #74) stays open until someone merges it manually, even when it only contains dependency bumps. Since wat is the core dependency of watify, releases with wat bumps should go out regularly without manual intervention.
Proposal
Add a scheduled workflow (weekly or monthly) that:
- Finds the open release-please PR (
chore(main): release x.y.z). - Checks whether its changelog includes a
watbump (e.g. achore(deps): bump wat from ...commit). - If so, merges the PR, which triggers the release and npm publish via the existing
release-please.ymlandpublish-npm.ymlworkflows.
Open questions
- Weekly or monthly cadence?
- Should bumps of other dependencies (e.g.
wasm-bindgen) also qualify, or onlywat?
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 reading the existing release-please.yml and publish-npm.yml workflows to understand how merging the release PR triggers a release and npm publish. Review the release-please PR format and changelog entries described in the issue, then resolve the cadence and dependency-scope questions. Done means a scheduled workflow identifies the relevant open PR, merges it when the wat-bump condition is met, and leaves other PRs untouched.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100