Last updated date appears to be incorrect

[michaelmior]

Description:
As the excerpt from the log below shows, I have a pull request that is identified as having been updated within the past several days even though the last update I can see is nearly one year ago.

[#514] Pull request #514
  [#514] Found this pull request last updated at: 2024-10-15T01:53:46Z

Action version:
v9

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Repro steps:
I am unsure how to reproduce this issue with a fresh repository, but here is an example of a run of this action that exhibits the problem.
For example, look at pull request 512.
It has not been updated in more than a year, but the action seems to think it was updated within the past several days.

Expected behavior:
The correct date of the last update should be identified.

Actual behavior:
The date of last update is not identified correctly.

[michaelmior]

I do see the updated_at date returned by the API is within the past several days, so I assume this is the root of the issue, but I don't see any user-facing updates visible. No commits pushed on the corresponding branch, no comments, no labels changed, etc.

[HarithaVattikuti]

Hello @michaelmior 👋,
Thank you for reporting this issue. We will investigate it and get back to you as soon as we have some feedback.

[dktapps]

Yep, running into this with a bunch of stale PRs on my repo too. For some reason a bunch of them got unmarked as stale 3 days ago. (Appears this may be to do with the base branch getting force-pushed???)

[Adam262Alloy]

I am noticing this in our repos as well. Taking three example PRs for example, they each have a comment from the Stale Github action that they were quickly marked and unmarked as stale on 1/6/25. Neither PR has user activity on that day (they are automated dependabot type PRs), and all should be stale in that they are older than our configured threshhold for staleness.

When I look in the Github action logs, I can see the action processed these PRs consecutively in the same batch, and they have very similar updated at messages:

PR 1 -- Found this pull request last updated at: 2025-01-06T22:22:13Z
PR 2 -- Found this pull request last updated at: 2025-01-06T22:22:13Z
PR 3 -- Found this pull request last updated at: 2025-01-06T22:22:14Z

[wandbjake]

Yeah, same thing when I tried on my repo. I think that the act of adding the Stale tag updates the updated_at. Github must've changed this internally, but this definitely breaks the logic. The first pass through it adds the tag, then the second pass it removes it.