build(deps): Bump arrow from 1.2.4 to 2.0.0

[dependabot]

Bumps arrow from 1.2.4 to 2.0.0.
Updates io.arrow-kt:arrow-core from 1.2.4 to 2.0.0

Release notes

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

2.0.0

The new major release of Arrow! 🎉

This version strives to be source compatible with 1.2, if deprecated methods and classes are not used. Please check the Arrow website for the full release notes.

2.0.0-rc.1

Release candidate for the new major version

2.0.0-beta.3

No release notes provided.

Changelog

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

Release flow

0. Previous checks

• No broken links in the website
• Dependencies in arrow-stack/build.gradle:
  • The new modules are considered
  • The old modules don't appear

1. Create a pull request

Prepare a pull request with these changes:

1. Update versions in arrow-libs/gradle.properties. For instance, the release version will be 0.10.5 and the next SNAPSHOT version will be 0.11.0-SNAPSHOT:

projects.version=0.11.0-SNAPSHOT
projects.latestVersion=0.10.5

2. Update versions in README.md

When merging that pull request, these things will happen automatically:

• New RELEASE version will be published for all the Arrow libraries into Sonatype staging repository.
• A tag will be created with the RELEASE version.
• Release notes will be created and associated to that tag.
• The website will be updated with a new RELEASE version (doc and doc/major.minor directories)

2. Close and release

Then, close and release the Sonatype repository to sync with Maven Central:

1. Login to https://oss.sonatype.org/ > Staging repositories
2. Check the content of the new staging repository
3. Select the staging repository and Close (it will check if the content meet the requirements)
4. Select the staging repository and Release to sync with Maven Central
5. Drop and repeat if there are issues.

NOTE: This plugin provides tasks for closing and releasing the staging repositories. However, that plugin must be applied to the root project, and it would be necessary to discard modules for publication. Let's keep this note here to give it a try later on.

About signing artifacts with GPG/PGP

One of the requirements for artifacts available in Central Maven is being signed with GPG/PGP.

These secrets are involved to meet that requirement:

• ORG_GRADLE_PROJECT_SIGNINGKEY: private key from Generating a Key Pair
• ORG_GRADLE_PROJECT_SIGNINGPASSWORD: passphrase from Generating a Key Pair

To verify artifacts during Close task, the public key must be distributed to a key server: Distributing Your Public Key.

... (truncated)

Commits

• 9131152 chore(deps): update all dependencies (#3541)
• e5fde90 chore(deps): update all dependencies (#3540)
• 89be074 chore(deps): update all dependencies (#3538)
• 3808d09 More overloads for collectors (#3539)
• 63b162f Prepare for 2.0 publication
• a203862 Add and fix contracts for inline functions (#3535)
• 5026cfd Defer optics generation of invalid classes to later ksp rounds (#3537)
• 2319143 chore(deps): update all dependencies (#3536)
• b490817 Change zipOrAccumulate to not use delegated properties to prevent IAE (#3533)
• 06ea5b9 Ensure AutoCloseScope and ResourceScope only ever call finalizers once (#3530)
• Additional commits viewable in compare view

Updates io.arrow-kt:arrow-optics from 1.2.4 to 2.0.0

Release notes

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

2.0.0

The new major release of Arrow! 🎉

This version strives to be source compatible with 1.2, if deprecated methods and classes are not used. Please check the Arrow website for the full release notes.

2.0.0-rc.1

Release candidate for the new major version

2.0.0-beta.3

No release notes provided.

Changelog

Sourced from io.arrow-kt:arrow-optics's changelog.

Release flow

0. Previous checks

• No broken links in the website
• Dependencies in arrow-stack/build.gradle:
  • The new modules are considered
  • The old modules don't appear

1. Create a pull request

Prepare a pull request with these changes:

1. Update versions in arrow-libs/gradle.properties. For instance, the release version will be 0.10.5 and the next SNAPSHOT version will be 0.11.0-SNAPSHOT:

projects.version=0.11.0-SNAPSHOT
projects.latestVersion=0.10.5

2. Update versions in README.md

When merging that pull request, these things will happen automatically:

• New RELEASE version will be published for all the Arrow libraries into Sonatype staging repository.
• A tag will be created with the RELEASE version.
• Release notes will be created and associated to that tag.
• The website will be updated with a new RELEASE version (doc and doc/major.minor directories)

2. Close and release

Then, close and release the Sonatype repository to sync with Maven Central:

1. Login to https://oss.sonatype.org/ > Staging repositories
2. Check the content of the new staging repository
3. Select the staging repository and Close (it will check if the content meet the requirements)
4. Select the staging repository and Release to sync with Maven Central
5. Drop and repeat if there are issues.

NOTE: This plugin provides tasks for closing and releasing the staging repositories. However, that plugin must be applied to the root project, and it would be necessary to discard modules for publication. Let's keep this note here to give it a try later on.

About signing artifacts with GPG/PGP

One of the requirements for artifacts available in Central Maven is being signed with GPG/PGP.

These secrets are involved to meet that requirement:

• ORG_GRADLE_PROJECT_SIGNINGKEY: private key from Generating a Key Pair
• ORG_GRADLE_PROJECT_SIGNINGPASSWORD: passphrase from Generating a Key Pair

To verify artifacts during Close task, the public key must be distributed to a key server: Distributing Your Public Key.

... (truncated)

Commits

• 9131152 chore(deps): update all dependencies (#3541)
• e5fde90 chore(deps): update all dependencies (#3540)
• 89be074 chore(deps): update all dependencies (#3538)
• 3808d09 More overloads for collectors (#3539)
• 63b162f Prepare for 2.0 publication
• a203862 Add and fix contracts for inline functions (#3535)
• 5026cfd Defer optics generation of invalid classes to later ksp rounds (#3537)
• 2319143 chore(deps): update all dependencies (#3536)
• b490817 Change zipOrAccumulate to not use delegated properties to prevent IAE (#3533)
• 06ea5b9 Ensure AutoCloseScope and ResourceScope only ever call finalizers once (#3530)
• Additional commits viewable in compare view

Updates io.arrow-kt:arrow-optics-ksp-plugin from 1.2.4 to 2.0.0

Release notes

Sourced from io.arrow-kt:arrow-optics-ksp-plugin's releases.

2.0.0

The new major release of Arrow! 🎉

This version strives to be source compatible with 1.2, if deprecated methods and classes are not used. Please check the Arrow website for the full release notes.

2.0.0-rc.1

Release candidate for the new major version

2.0.0-beta.3

No release notes provided.

Changelog

Sourced from io.arrow-kt:arrow-optics-ksp-plugin's changelog.

Release flow

0. Previous checks

• No broken links in the website
• Dependencies in arrow-stack/build.gradle:
  • The new modules are considered
  • The old modules don't appear

1. Create a pull request

Prepare a pull request with these changes:

1. Update versions in arrow-libs/gradle.properties. For instance, the release version will be 0.10.5 and the next SNAPSHOT version will be 0.11.0-SNAPSHOT:

projects.version=0.11.0-SNAPSHOT
projects.latestVersion=0.10.5

2. Update versions in README.md

When merging that pull request, these things will happen automatically:

• New RELEASE version will be published for all the Arrow libraries into Sonatype staging repository.
• A tag will be created with the RELEASE version.
• Release notes will be created and associated to that tag.
• The website will be updated with a new RELEASE version (doc and doc/major.minor directories)

2. Close and release

Then, close and release the Sonatype repository to sync with Maven Central:

1. Login to https://oss.sonatype.org/ > Staging repositories
2. Check the content of the new staging repository
3. Select the staging repository and Close (it will check if the content meet the requirements)
4. Select the staging repository and Release to sync with Maven Central
5. Drop and repeat if there are issues.

NOTE: This plugin provides tasks for closing and releasing the staging repositories. However, that plugin must be applied to the root project, and it would be necessary to discard modules for publication. Let's keep this note here to give it a try later on.

About signing artifacts with GPG/PGP

One of the requirements for artifacts available in Central Maven is being signed with GPG/PGP.

These secrets are involved to meet that requirement:

• ORG_GRADLE_PROJECT_SIGNINGKEY: private key from Generating a Key Pair
• ORG_GRADLE_PROJECT_SIGNINGPASSWORD: passphrase from Generating a Key Pair

To verify artifacts during Close task, the public key must be distributed to a key server: Distributing Your Public Key.

... (truncated)

Commits

• 9131152 chore(deps): update all dependencies (#3541)
• e5fde90 chore(deps): update all dependencies (#3540)
• 89be074 chore(deps): update all dependencies (#3538)
• 3808d09 More overloads for collectors (#3539)
• 63b162f Prepare for 2.0 publication
• a203862 Add and fix contracts for inline functions (#3535)
• 5026cfd Defer optics generation of invalid classes to later ksp rounds (#3537)
• 2319143 chore(deps): update all dependencies (#3536)
• b490817 Change zipOrAccumulate to not use delegated properties to prevent IAE (#3533)
• 06ea5b9 Ensure AutoCloseScope and ResourceScope only ever call finalizers once (#3530)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 <dependency name> 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Superseded by #800.