🔖(deps): Update tj-actions/changed-files digest to 0e58ed8

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
tj-actions/changed-files	action	digest	9200e69 -> 0e58ed8

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[xnox]

tj-actions/changed-files#2463

Please revert

[monperrus]

@LogFlames already reverted or not? of not could you do it?

[algomaster99]

Yes, it is handled. @LogFlames rebased the commit out of main branch.

[algomaster99]

I put the back the commit 964b103 (after rebasing it is 0501803) and reverted that in b92eb94. This is done in order to maintain a transparent commit log. Thanks @xnox !

@LogFlames the current commit (b92eb94) on main fails because action/checkout cannot be downloaded. Could you help me debug this?

[monperrus]

FTR, revert commit is 3704f37

[LogFlames]

@algomaster99

@LogFlames the current commit (b92eb94) on main fails because action/checkout cannot be downloaded. Could you help me debug this?

CI is now up and running again. Seems tj-actions/changed-files had been banned/depricated/removed in some way, even the older sha which we reverted to. This lead to any action containing it could not be run in chains-project/maven-lockfile (but could be ran in LogFlames/maven-lockfile-action-test-project for example)

The error is very weird and non descriptive, if I removed actions/checkout from the maven-lockfile action the next action (actions/setup-java) was the one that got the same "Missing download info" error.

Also, because we cannot release without using the action an interim non-release action sha had to be used where tj-actions/changed-files was removed.

[algomaster99]

but could be ran in LogFlames/maven-lockfile-action-test-project for example

That's weird. It seems the restriction is project based which makes me question what projects it won't work on.

Also, because we cannot release without using the action an interim non-release action sha had to be used where tj-actions/changed-files was removed.

Makes sense.