-
Notifications
You must be signed in to change notification settings - Fork 887
Improve release process #4074
Comments
We don't do this because we wanted to allow external maintainers from outside Palantir, but restrict publishing privileges to Palantir maintainers (see #2985). |
Yeah that makes sense. It seems that since we don't have any external maintainers contributing any more, we may as well prune the list and enable publishing on CI. Either that, or the second-best option which would be to create a |
Gotcha! |
💀 It's time! 💀TSLint is being deprecated and no longer accepting pull requests for major new changes or features. See #4534. 😱 If you'd like to see this change implemented, you have two choices:
👋 It was a pleasure open sourcing with you! If you believe this message was posted here in error, please comment so we can re-open the issue! |
🤖 Beep boop! 👉 TSLint is deprecated 👈 (#4534) and you should switch to typescript-eslint! 🤖 🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋 |
Current the release process takes a long time, and is a manual process. It would be good to improve it to the point where we can "one click release" for major/minor/patch versions, and maybe even have nightlies or weeklies based on
master
.The major pain points with the release process right now are:
gh-pages
to generate the documentation (also on CI)@giladgray for SA
The text was updated successfully, but these errors were encountered: