oxidecomputer / oxidecomputer/oxide.ts
Automate publishing to npm + changelogs
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 33
- Forks
- 4
- Avg merge
- 6d 9h
- Merged PRs (30d)
- 4
Description
Followup to https://github.com/oxidecomputer/oxide.ts/pull/240. Some interesting tools for this:
- https://github.com/semantic-release/semantic-release
- https://intuit.github.io/auto/ (used by design-system)
- https://github.com/release-it/release-it
- https://github.com/changesets/changesets
- https://lerna.js.org/ (probably overkill)
Not sure whether we want to automatically release @oxide/api, but we can definitely test this out on the generator package.
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 pull request 240 and the generator package, then compare the listed release tools against the repository's current publishing setup. Done means an agreed automation approach publishes the generator package and produces changelogs, with the scope of @oxide/api explicitly decided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100