Releases feature

• documentation
• API
• API documentation

Continue of !1752 (merged)

Part of #2701 (closed)

Any chance @jschoeffling gets name checked in the 8.2 changelog for this feature (he did all the heavy lifting).

@dzaporozhets What happens to uploaded binaries, which are uploaded to the release, when deleting the tag? IMHO the binaries should be deleted as well. I think this nowhere implemented in GitLab right now.

@razer6 nothing happens to attachments. But why bother deleting it? I think we dont do it for files attached to comments either

But these attachments are dead links. No link to that file anymore. It's the same for issues/comments.

I do think GitLab should delete the attachments when they are removed from comments, and the same goes for the uploaded binaries. Sensitive attachments have been accidentally added on GitLab.com, and removing the link gives the false impression that the attachment is no longer available. I do realize that it's tricky to ensure that there no more references exist to an attached file, though.

Added 63 commits:

• d1edc1e2...329a5555 - 61 commits from branch master
• 3c96ea76 - Fix changelog item
• 2ac11937 - Add release notes documentation

Added 4 commits:

• a5ab56fd - Move git tags API to separate file
• d343d9d8 - Add grape routing print
• c119a737 - Add releases api
• ba34045f - Expose release notes to tags api

Added 2 commits:

• 8f53094f - Add API docs and correctly expose release api
• d6db4517 - Add api test for creating tag with release info

@DouweM can you review?

@vsizov can you review?

👍

Added 1 commit:

• 743d66e4 - Improve english text

Status changed to merged

@dzaporozhets I looked at the API and I think it would make more sense to change the endpoint from PUT /projects/:id/repository/tags to PUT /projects/:id/repository/tags/:tag. I can make this change, but this should got into 8.2. @stanhu What do you think?

Furtheremore, shouldn't the field tag be changed to tag_name to be consistent with other API methods.

@razer6 Yes, I think making the API PUT /projects/:id/repository/tags/:tag_name/release makes the API consistent. We should make the change for 8.2.

I'll make a MR

There is another thing. The API responds with

{
  "tag": "1.0.0",
  "description": "Amazing release. Wow"
}

This should be changed to tag_name as well.

Ok for consistency 😃