Remove workarounds now that TileDB 2.30.0 has been released

[jdblischak]

Closes #232

xref: #224, conda-forge/tiledb-feedstock#470

[jdblischak]

Successful manual run: https://github.com/TileDB-Inc/conda-forge-nightly-controller/actions/runs/20033361783

[teo-tsirpanis]

LGTM

I've thought about this recently, and I must say that I don't see much value in running Conda nightly builds. TileDB's build system has stabilized a lot with vcpkg, and immediately reacting to any buid system or dependency changes in main (which we will have to do on the main feedstock after a release either way) is more work with little apparent benefit.

[jdblischak]

I've thought about this recently, and I must say that I don't see much value in running Conda nightly builds. TileDB's build system has stabilized a lot with vcpkg, and immediately reacting to any buid system or dependency changes in main (which we will have to do on the main feedstock after a release either way) is more work with little apparent benefit.

The goal is to ensure the feedstock update goes smoothly when a new version is released. We don't want to delay a release because of an obscure conda build problem or because a dependency is missing from conda-forge. As a case in point, the recent feedstock PR for 2.30 (conda-forge/tiledb-feedstock#470) went smoothly because we already knew exactly which recipe updates needed to be made (#224, conda-forge/tiledb-feedstock@0e95785).

[teo-tsirpanis]

The goal is to ensure the feedstock update goes smoothly when a new version is released. We don't want to delay a release because of an obscure conda build problem or because a dependency is missing from conda-forge.

Yes, but this results in at least 3x the PRs for an upstream dependency change (add workarounds to this repo, update the main feedstock when the release gets tagged, and revert the workarounds added in step 1). The dependency changes can be seen by viewing the diff of vcpkg.json between releases (there's also that Azure SDK patch, but that was because they made a breaking change).

conda-forge/tiledb-feedstock is also not part of the TileDB Cloud release process since the introduction of the for-cloud label, so a slight delay in updating it would not be significant.