Bitrise API
/release-management/v1/* version retirement
Deprecated, no dateSubscribe to Bitrise APIShare
Bitrise deprecated the /release-management/v1/* endpoints without a shutdown date. Calls made to these endpoints will eventually fail. Bitrise API notes that v1 is deprecated.
Calls it hits
/release-management/v1/*
What to use instead of these calls
Move to Release Management API v2, including its Apps, Build Distributions, Store Releases, and Code Push sub-APIs under api.bitrise.io/release-management/v2/. The app id becomes a query parameter instead.
In Bitrise API's words
v1: https://api.bitrise.io/release-management/v1 . This is deprecated.
Facts
- API
- Bitrise API
api.bitrise.io - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Bitrise API's own pages
Questions
When does this change take effect?
Bitrise API deprecated /release-management/v1/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Bitrise API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Bitrise API 2
-
No date
GET /v0.1/apps/{id}/secrets/{id}/valueEndpoint removal Deprecated, no date -
No date
PUT /v0.1/apps/{id}/secrets/{id}Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.