Commit 58c297f8 authored by Amy Qualls's avatar Amy Qualls

Merge branch 'ap-releases-api' into 'master'

Update upcoming releases API docs

See merge request gitlab-org/gitlab!60395
parents d3e70a87 a15684c7
...@@ -717,6 +717,5 @@ Example response: ...@@ -717,6 +717,5 @@ Example response:
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/38105) in GitLab 12.1. > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/38105) in GitLab 12.1.
A release with a `released_at` attribute set to a future date is labeled an **Upcoming Release** in the UI: A release with a `released_at` attribute set to a future date is labeled
as an **Upcoming Release** [in the UI](../../user/project/releases/index.md#upcoming-releases).
![Upcoming release](img/upcoming_release_v12_1.png)
...@@ -86,7 +86,7 @@ by using a `release` node in the job definition. ...@@ -86,7 +86,7 @@ by using a `release` node in the job definition.
The release is created only if the job processes without error. If the Rails API returns an error The release is created only if the job processes without error. If the Rails API returns an error
during release creation, the release job fails. during release creation, the release job fails.
### Schedule a future release ### Upcoming releases
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/38105) in GitLab 12.1. > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/38105) in GitLab 12.1.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment