microsoft / microsoft/DefinitelyTyped-tools
Support beta builds of DT packages?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 423
- Forks
- 237
- Avg merge
- 18h 18m
- Merged PRs (30d)
- 11
Description
Let's take a big PR like "add Node 16" - today it's tested via the .d.ts files and humans look over and guestimate whether this is going to break projects.
We could support: "@typescript-bot pack this" which would trigger a HTTP call to the publisher bot, instead of running main() it would:
- change
definitelyTypedZipUrlto be the zip for the PR ( e.g. https://codeload.github.com/DefinitelyTyped/DefinitelyTyped/tar.gz/pull/52357/head ) - take the packages to deploy from the bot request
- deploy the version as a different npm tag, and not as 'latest' so people don't get it by default
Happy to pair on this if folks are interested
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 tracing main() and the publisher-bot request path, then inspect where definitelyTypedZipUrl and package deployment tags are handled. Confirm how a PR archive and requested packages would reach the deployment flow. Done means a bot request can publish selected PR packages under a non-latest npm tag without changing the default release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100