Why does a project show "Updated 4 days ago" when it hasn't been updated for three months?

When I list my projects one of them, a private repo, is shown “Updated 4 days ago” but the last commit was 3 months ago. I am the only person who has access to this repo and I haven’t done anything like create a wiki page. What else can there be that’s causing it to show it as having been updated so recently ?

1 Like

I’ve got the same problem.

Have you found a solution?

1 Like

No, as far as I recall I never found a solution. I don’t know which repos I was looking at at the time but i’ve just gone and looked at a private repos in my account and the last commit is 2018 and the ‘Updated’ value is 2022.

I have just thought of one thing. At some point in the last few years I have migrated repos from Bitbucket to Gitlab and the ‘Updated’ might reflect the import rather than the most recent commit. A reason this is not so likely is that the I’m pretty sure the Bitbucket imports were before 2022 and also I would expect the wrong ‘Updated’ values to be clustered around a single, short, period of time when I was importing a number of repos and they’re not.

Sorry not to be able to help.

1 Like

Got the same. Old repos, which were not used for some years, became “updated few hours ago”.

1 Like

Yes this is very worrying it has happened before to me and it happened again. It looks as if someone is tampering with the repositories and it is to such an extend that it involves all repositories with several being changed each day. I resolved to removing all my SSH keys and changing the password…This is so troublesome to me and I am even considering switching to another company and moving all my projects there…Of course I am on the free tier nobody is answering my messages whatsoever…

I have a similar thing on one of my projects. Commit from 4 years ago, last updated on June 06 2023. I used the Projects API command to see the actual date/time that the last update occurred. I checked under Manage → Activity and obviously it’s completely empty. No commits, no issues, no wiki, nothing has been done on the project.

Now, since I haven’t done any changes, I then decided to check what I was doing on or around that time by checking my log files. I expected potentially that I updated my system, and Gitlab was updated and some queued processes in Gitlab were responsible for it. Perhaps migrations or whatever.

Anyway, on June 05 2023 at around 20:07 I had completed upgrade to Gitlab 16.0.2 which you can see here:

2023-06-05 20:01:51 startup archives unpack
2023-06-05 20:02:00 upgrade gitlab-ce:amd64 16.0.1-ce.0 16.0.2-ce.0
2023-06-05 20:02:00 status half-configured gitlab-ce:amd64 16.0.1-ce.0
2023-06-05 20:02:00 status unpacked gitlab-ce:amd64 16.0.1-ce.0
2023-06-05 20:02:00 status half-installed gitlab-ce:amd64 16.0.1-ce.0
2023-06-05 20:05:19 status unpacked gitlab-ce:amd64 16.0.2-ce.0
2023-06-05 20:05:44 startup packages configure
2023-06-05 20:05:44 configure gitlab-ce:amd64 16.0.2-ce.0 <none>
2023-06-05 20:05:44 status unpacked gitlab-ce:amd64 16.0.2-ce.0
2023-06-05 20:05:44 status half-configured gitlab-ce:amd64 16.0.2-ce.0
2023-06-05 20:07:35 status installed gitlab-ce:amd64 16.0.2-ce.0

therefore I expect that perhaps your Gitlab was upgraded recently prior to the last update time, and Gitlab’s scheduled tasks via cron/sidekiq were responsible for that.

See this Gitlab issue too which explains even more: "Updated at" time incorrect in list of projects (#432410) · Issues · GitLab.org / GitLab · GitLab

1 Like

happened to me as well. ive’ opened to ticket gitlab.com: project that i did not Touch for years pops up "updated X hours ago" - how come? (#435169) · Issues · GitLab.org / GitLab · GitLab