-
Notifications
You must be signed in to change notification settings - Fork 73
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.
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
Remove/replace Shipkit #410
Comments
I guess it's 'have converted' because 'Several customers inclusing Mockito project have already migrated'. Maybe we should just copy Mockito? 🤷 |
Oh cool, I will take a look tomorrow evening |
Updating Shipkit is already 'in-progress' because dependabot opened #400. |
Now Shipkit is split to new separate projects: |
If nobody is working on it, I can try do it in a few days. |
and PR #419 |
I've just got a mail from GitHub (full text below) that they revoked my read-only OAuth token that we used for ShipKit. I was a bit surprised at first - after all, what's the harm in sharing a read-only token? Only thing I could come up with was that other people could use it to circumvent rate-limiting. Either way, we need a new way to implement this because I assume future tokens would share the same fate (sooner or later). @aepfli Was there a reason why this token was not also passed in as an environment variable? @slawekjaranowski First of all, hi! 👋🏾 Thanks for taking up this task - it may take a few days before I get to look at your PR, but that doesn't change that it is highly appreciated. Don't forget to add yourself to the README as described here. If you haven't already, can you take this opportunity to replace the token with a System environment variable called
|
I never ever touched this token :D - would have been a good idea - it is from long time ago, even before our migration to Github actions. |
mentioned token will be remove in my PR |
Migrate to new Shipkit plugins (#410 / #419) Shipkit is deprecated and the GitHub project[1] is archived. They write: > "One Shipkit Gradle plugin to rule them all" approach has proven > hard to maintain for the team. We [have] converted Shipkit into a > narrow set of small libraries (design note[2]). Several customers, > inclu[d]ing Mockito project have already migrated. More preecisely, Shipkit was split into these projects: * shipkit-auto-version[3] * shipkit-changelog[4] * shipkit-github-release (no source on GitHub?) This change updates the build accordingly. Closes: #410 Maybe solves: #256 (can't be determined without a release build) PR: #419 [1]: https://github.com/mockito/shipkit [2]: https://github.com/mockito/shipkit/blob/master/docs/design-specs/future-shipkit.md [3]: https://github.com/shipkit/shipkit-auto-version [4]: https://github.com/shipkit/shipkit-changelog
Shipkit is deprecated and the GitHub project is archived. They write:
We need to investigate whether there is already a replacement ("We are converted" is an unfortunate mistake because it could be "have converted" or "are converting") and then possibly migrate to it. This may also fix #246.
On a side note: Our version of Shipkit uses a deprecated GitHub API that stops working in May. It was fixed, though, so this could be solved by updating Shipkit.
The text was updated successfully, but these errors were encountered: