microsoft / microsoft/beachball
Advice on Nightly Builds
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 815
- Forks
- 93
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 12
Description
We're looking at adopting Beachball, but in addition to our standard releases, we need nightly releases tagged as dev on NPM. Is there a way to use Beachball to publish do a dev tag on NPM where it adds a pre-release version based on date only, without updating the semver? e.g. 1.2.0-dev.20201021, 1.2.0-dev.20201022, 1.2.0-dev.20201023
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 reading Beachball's release and NPM publishing documentation and entry points to determine how prerelease versions and distribution tags are handled. Done means establishing whether date-based dev versions can be published without advancing the standard semver version, and documenting the required configuration or implementation scope.
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
- 20/100