Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,329
    • Merge requests 1,329
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #16821
Closed
Open
Issue created Jan 02, 2017 by Balasankar 'Balu' C@balasankarcDeveloper

Permanent link to latest version of a release

Description

Related to/ Extended from : gitlab-ce#22273

Now that we have the GitLab Releases feature (https://gitlab.com/gitlab-org/gitlab-ce/issues/41766), we should make sure that it is as easy to use as possible. Retrieving a link to source or an asset should be possible using a predictable URL. Something like /releases/11.4/source.tar.gz, releases/11.4/installer.dmg, and so on. In the interest of making this easy to use, we should also support a way to point to latest:

In this example, /releases/latest/installer.dmg could substitute latest with 11.4. We may need some kind of syntax to differentiate the latest tag from a release that's unfortunately named "latest."

Proposal

Because internally these are all links, it should be possible to handle all of this through redirects i.e.:

If the URL for installer.dmg is http://download.com/myrelease/11.4/installer.dmg, visiting /releases/11.4/installer.dmg should result in a redirect to the internal or external site (we should show a heads up message if we are redirecting to an external site).

Similarly, visiting latest, if latest is 11.4, we can follow the redirects to get to the right asset eventually, so: /releases/latest/installer.dmg

Use-case

Suppose I use GitLab.com to host my software project and uses GItLab CI to build the software. I could easily link to the latest version of the software from my website, without having to edit the website each time I push a new version to modify the link.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Release notes

Documentation: https://docs.gitlab.com/ee/user/project/releases/#permanent-link-to-latest-release We have added a link to the latest release for a project. This makes it easier to navigate to the latest release without needing to know or change version numbers.

Edited Mar 11, 2022 by Chris Balane
Assignee
Assign to
Time tracking