Changelog button doesn't open the correct file

Summary

(Not sure this is a bug or I'm just using it wrong)

The CHANGELOG button, present on the project's main page, opens the wrong file.

image

I had a project with a really long CHANGELOG.md file, so I decided to archive the existing changelog (into the CHANGELOG-archive.md) and create a new one (CHANGELOG.md). Howevere after doing this, the CHANGELOG button still opens the archived changelog.

Steps to reproduce

  1. Create a CHANGELOG.md file
  2. Rename that file to CHANGELOG-archive.md
  3. Create another CHANGELOG.md file
  4. Check that the CHANGELOG button still points to the CHANGELOG-archive.md file

Example Project

https://gitlab.com/jcamilo93/buggy-behaviour

What is the current bug behavior?

The CHANGELOG button does not open the correct file.

What is the expected correct behavior?

When clicking the CHANGELOG button it should open the CHANGELOG.md file

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Edited by 🤖 GitLab Bot 🤖