Bump io.arrow-kt:arrow-core from 1.2.3 to 1.2.4

[dependabot[bot]]

Bumps io.arrow-kt:arrow-core from 1.2.3 to 1.2.4.

Release notes

Sourced from io.arrow-kt:arrow-core's releases.

1.2.4

1 Bug fixes:

• New AutoCloseScope DSL, make sure closing in reversed order

1 Rollback:

• Don't be too strict on return type of Raise DSL.

What's Changed

• chore(deps): update all dependencies by @​renovate in arrow-kt/arrow#3383
• fix(autoclose): close Closeables in reversed order by @​hoc081098 in arrow-kt/arrow#3387
• chore(deps): update all dependencies by @​renovate in arrow-kt/arrow#3392
• fix: Fold restriction not allowing any Function to be returned is too strict in https://github.com/arrow-kt/arrow/commit/4bd8694146be868aa6ac76e0a48e34a6e160d8ca

Full Changelog: https://github.com/arrow-kt/arrow/compare/1.2.3...1.2.4

Commits

• 4bd8694 Revert foldUnsafe
• 4cd0947 chore(deps): update all dependencies (#3392)
• 484c0a2 fix(autoclose): close Closeables in reversed order (#3387)
• e0a13f1 chore(deps): update all dependencies (#3383)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions[bot]]

Qodana Community for JVM

1 new problem were found

Inspection name	Severity	Problems
Class member can have 'private' visibility	◽️ Notice	1

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either: 1. Register at [Qodana Cloud](https://qodana.cloud/) and [configure the action](https://github.com/jetbrains/qodana-action#qodana-cloud) 2. Use [GitHub Code Scanning with Qodana](https://github.com/jetbrains/qodana-action#github-code-scanning) 3. Host [Qodana report at GitHub Pages](https://github.com/JetBrains/qodana-action/blob/3a8e25f5caad8d8b01c1435f1ef7b19fe8b039a0/README.md#github-pages) 4. Inspect and use `qodana.sarif.json` (see [the Qodana SARIF format](https://www.jetbrains.com/help/qodana/qodana-sarif-output.html#Report+structure) for details) To get `*.log` files or any other Qodana artifacts, run the action with `upload-result` option set to `true`, so that the action will upload the files as the job artifacts: ```yaml - name: 'Qodana Scan' uses: JetBrains/qodana-action@v2023.3.1 with: upload-result: true ```

Contact Qodana team

Contact us at [qodana-support@jetbrains.com](mailto:qodana-support@jetbrains.com) - Or via our issue tracker: https://jb.gg/qodana-issue - Or share your feedback: https://jb.gg/qodana-discussions