Skip to content
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.

Improve release process #4074

Closed
johnwiseheart opened this issue Jul 28, 2018 · 5 comments
Closed

Improve release process #4074

johnwiseheart opened this issue Jul 28, 2018 · 5 comments

Comments

@johnwiseheart
Copy link
Contributor

johnwiseheart commented Jul 28, 2018

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:

  • Cleaning up the changelog
    • We should consider enforcing changelog changes with every PR so that this is not a manual process
  • Publishing the release itself
    • We should consider generating a token and putting it into CircleCI such that we can publish in CI rather than locally.
  • Releasing docs
    • We should consider using gh-pages to generate the documentation (also on CI)

@giladgray for SA

@adidahiya
Copy link
Contributor

We should consider generating a token and putting it into CircleCI such that we can publish in CI rather than locally.

We don't do this because we wanted to allow external maintainers from outside Palantir, but restrict publishing privileges to Palantir maintainers (see #2985).

@johnwiseheart
Copy link
Contributor Author

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 publish script which does all the above steps, but still has to be run locally.

@JoshuaKGoldberg
Copy link
Contributor

don't have any external maintainers contributing any more

Gotcha!

@JoshuaKGoldberg
Copy link
Contributor

💀 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:

  • Recommended: Check if this is available in ESLint + typescript-eslint
  • Not Recommended: Fork TSLint locally 🤷‍♂️

👋 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!

@JoshuaKGoldberg
Copy link
Contributor

🤖 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! 👋

@palantir palantir locked and limited conversation to collaborators Mar 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants