chore(deps): update jetbrains/qodana-action action to v2023

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
JetBrains/qodana-action	action	major	v2022.3.4 -> v2023.1.0

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

Release Notes

JetBrains/qodana-action

v2023.1.0

Compare Source

Changelog

• 5e14015 ⬆️ Bump xml2js, @​azure/ms-rest-js and @​azure/storage-blob
• ddd70ab 🚸 Improve GitHub action summary
• bdbf6e5 ⚡ Update qodana to 2023.1.0
• 9f2af3f ⚡ Allow setting cache keys on GitHub and CircleCI (#​107)
• 61b94e7 ⚡ Add licenses preview to job output

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Mend Renovate. View repository job log here.

[MartinWitt]

This requires atleast an update of the linter in our qodana.yml file. But also the config format was improved. I will push a fix for this dependency with the new config soon.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[MartinWitt]

Looks like our old config still works. I prefer to not touch it if it works. If you want to have a look at the changelogs, see https://blog.jetbrains.com/qodana/2023/04/qodana-2023-1/#FlexibleprofileconfigurationwiththenewYAMLformat

[SirYwell]

Do we need to specify the linter explicitly in the qodana.yaml? How does that differ from the action?

[MartinWitt]

Do we need to specify the linter explicitly in the qodana.yaml? How does that differ from the action?

There was an warning message written if you don't specific your linter that you should setup Qodana with qodana init. We can accept this message and remove the linter in qodana.yml if you want.

[SirYwell]

Do we need to specify the linter explicitly in the qodana.yaml? How does that differ from the action?

There was an warning message written if you don't specific your linter that you should setup Qodana with qodana init. We can accept this message and remove the linter in qodana.yml if you want.

Hm, that doesn't sound great either, but if it works and we don't need to manually update the version ourselves, it might be a bit better.

[MartinWitt]

Do we need to specify the linter explicitly in the qodana.yaml? How does that differ from the action?

There was an warning message written if you don't specific your linter that you should setup Qodana with qodana init. We can accept this message and remove the linter in qodana.yml if you want.

Hm, that doesn't sound great either, but if it works and we don't need to manually update the version ourselves, it might be a bit better.

I removed the linter. Lets give it a try?

[I-Al-Istannen]

! No valid qodana.yaml found. Have you run qodana init? Running that for you...
Seems like the file is no longer valid. Have you tried setting the linter version to latest?

[MartinWitt]

https://youtrack.jetbrains.com/issue/QD-4217/No-valid-qodana.yaml-found-even-though-it-is-present as you see here it is only a warning.

[MartinWitt]

! No valid qodana.yaml found. Have you run qodana init? Running that for you... Seems like the file is no longer valid. Have you tried setting the linter version to latest?

Setting to latest means we will update the qodana linter silently if there is any update. This seems not ideal for a CI?

[SirYwell]

Okay, let's go this way then.