Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release Automation Meta Issue #37196

Open
1 of 3 tasks
DanielRosenwasser opened this issue Mar 3, 2020 · 1 comment
Open
1 of 3 tasks

Release Automation Meta Issue #37196

DanielRosenwasser opened this issue Mar 3, 2020 · 1 comment
Labels
Infrastructure Issue relates to TypeScript team infrastructure Meta-Issue An issue about the team, or the direction of TypeScript

Comments

@DanielRosenwasser
Copy link
Member

We're trying to find ways to reduce the amount of manual work that a release requires. This currently includes

More may be added to this list over time
@DanielRosenwasser DanielRosenwasser added Infrastructure Issue relates to TypeScript team infrastructure Meta-Issue An issue about the team, or the direction of TypeScript labels Mar 3, 2020
@DanielRosenwasser DanielRosenwasser mentioned this issue Mar 3, 2020
Closed
@orta
Copy link
Contributor

orta commented Sep 11, 2020

It doesn't look like we deploy the main npm packages through automation, but I think I can make it so publishing a new release could trigger a build for the playground (via the same mechanism we do PR deploys)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Infrastructure Issue relates to TypeScript team infrastructure Meta-Issue An issue about the team, or the direction of TypeScript
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@orta @DanielRosenwasser