Migrate release process to Shipkit
See original GitHub issueSimilar to mockito-core
and mockito-scala
, let’s migrate the release process to Shipkit. The Maven Central artifact location should become https://repo1.maven.org/maven2/org/mockito/kotlin/mockito-kotlin/
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Release Notes: SharePoint Migration Tool (SPMT)
Learn about the new features and updates to existing features in SharePoint Migration Tool in these release notes.
Read more >Migrate to versioned snippets Rake tasks - GitLab Docs
The following Rake tasks help with that process. Migrate specific snippets to Git. In case you want to migrate a range of snippets,...
Read more >Migrate to a New Version | Campaign Manager 360
Migrate to a New Version · Step 1: Determine which version you're using · Step 2: Determine the status of your version ·...
Read more >Shipkit — getting started - Smart Up
Automated versioning, generating release notes and publishing are, ... you how you can start using ShipKit in your project in 15 minutes.
Read more >Migrating a Version 5 deployment - IBM
Use the appropriate procedure for migrating extensions to either a v10 DataPower® Gateway (v5 compatible) or a v10 DataPower API Gateway. Migration ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed 🎉
@TimvdLippe I just included the new artifact in our project, works fine!