This commit adds an id attribute to release blocks to allow them to be
targeted as anchor links.

Disables the vue-i18n eslint rules for files
that are not able to be autofixed, this will
stop these offences causing pipeline failures
but they will need manual fixing.

Jason Goodman authored 5 years ago and Nick Thomas committed 5 years ago

Add released_at field to releases API
Add released_at column to releases table
Return releases to the API sorted by released_at

E'zeki&el Kigbo authored 5 years ago and Filipa Lacerda committed 5 years ago

i18n linting for .vue files under the directories:
- app/assets/javascripts/error_tracking_settings
- app/assets/javascripts/filtered_search
- app/assets/javascripts/projects
- app/assets/javascripts/releases
- app/assets/javascripts/repository

When a release is a pre release, we render
an orange badge with `pre-release` label

This is step one of resolving
https://gitlab.com/gitlab-org/gitlab-ce/issues/56838.

Here is what changed:
- Revert the security fix from bdee9e84.
- Do not leak repository information (tag name, commit) to guests in API
responses.
- Do not include links to source code in API responses for users that do
not have download_code access.
- Show Releases in sidebar for guests.
- Do not display links to source code under Assets for users that do not
have download_code access.

GET ':id/releases/:tag_name' still do not allow guests to access
releases. This is to prevent guessing tag existence.

In releases page, instead of rendering
a loading icon, it now renders the skeleton loading