Update `org.playframework.play` to `v3.1.0-70605848-SNAPSHOT` (was `3.1.0-d1f1b9f8-SNAPSHOT`)

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.playframework.play	3.1.0-d1f1b9f8-SNAPSHOT -> 3.1.0-70605848-SNAPSHOT

---

Configuration

📅 Schedule: Branch creation - "monthly" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[ihostage]

So, Matthias... We caught the situation that I meant when asked you about reason to have a SHA part in snapshots version.

v3.1.0-70605848-SNAPSHOT was published at Jul 29 17:19:45 UTC 2024, but v3.1.0-d1f1b9f8-SNAPSHOT is a real latest version that was published at Jul 31 10:28:46 UTC 2024.

I'm not sure that Renovate can help us in this situation that why I update the Play for main branch manually.

I see a two ways:

1. Drop the sha part for publication snapshots version for Playframework
2. Configure Renovate not to bump the Play version for main branch.

What is your opinion?

[renovate[bot]]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

[mkurz]

This question is still open...

[ihostage]

Yes, it is 😄