| item_id,type,project,old_version,new_version,claim,question,how_to_check |
| C029,breaking_change_claim,apache-airflow,1.10.15,2.0.1,`airflow.configuration.mkdir_p` can be used in 1.10.15 but no longer exists in 2.0.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'apache-airflow==1.10.15'` and `pip install 'apache-airflow==2.0.1'`; in each run `python check_item.py airflow.configuration.mkdir_p`. Release notes, changelogs and documentation are also valid evidence." |
| C005,breaking_change_claim,azure-mgmt-storage,24.0.1,25.0.0,`azure.mgmt.storage.models.ProxyResourceAutoGenerated` can be used in 24.0.1 but no longer exists in 25.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-storage==24.0.1'` and `pip install 'azure-mgmt-storage==25.0.0'`; in each run `python check_item.py azure.mgmt.storage.models.ProxyResourceAutoGenerated`. Release notes, changelogs and documentation are also valid evidence." |
| C042,breaking_change_claim,jaxlib,0.5.3,0.6.0,`jaxlib.triton.dialect.experimental_descriptor_scatter` can be used in 0.5.3 but no longer exists in 0.6.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'jaxlib==0.5.3'` and `pip install 'jaxlib==0.6.0'`; in each run `python check_item.py jaxlib.triton.dialect.experimental_descriptor_scatter`. Release notes, changelogs and documentation are also valid evidence." |
| P242,benchmark_pair,pdf2image,1.16.0,1.16.2,"This snippet works with pdf2image==1.16.0 and fails with pdf2image==1.16.2 (because of `pdf2image.pdfinfo_from_bytes`, param_renamed `pdf_file`): |
| from pdf2image import pdfinfo_from_bytes |
| pdfinfo_from_bytes(pdf_file=...)",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `pdf2image.pdfinfo_from_bytes`, not from the placeholder arguments." |
| C082,breaking_change_claim,mypy-boto3-rds,1.36.0,1.36.11,`mypy_boto3_rds.type_defs.DescribeDBClustersMessageRequestTypeDef` can be used in 1.36.0 but no longer exists in 1.36.11.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'mypy-boto3-rds==1.36.0'` and `pip install 'mypy-boto3-rds==1.36.11'`; in each run `python check_item.py mypy_boto3_rds.type_defs.DescribeDBClustersMessageRequestTypeDef`. Release notes, changelogs and documentation are also valid evidence." |
| C103,breaking_change_claim,hatch,1.7.0,1.8.0,`hatch.cli.terminal.MockStatus` can be used in 1.7.0 but no longer exists in 1.8.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'hatch==1.7.0'` and `pip install 'hatch==1.8.0'`; in each run `python check_item.py hatch.cli.terminal.MockStatus`. Release notes, changelogs and documentation are also valid evidence." |
| C121,breaking_change_claim,jaxlib,0.9.0.1,0.9.1,`jaxlib.mlir.dialects.arith.DenormalMode` can be used in 0.9.0.1 but no longer exists in 0.9.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'jaxlib==0.9.0.1'` and `pip install 'jaxlib==0.9.1'`; in each run `python check_item.py jaxlib.mlir.dialects.arith.DenormalMode`. Release notes, changelogs and documentation are also valid evidence." |
| C158,breaking_change_claim,xarray,2026.7.0,2026.9.0,`xarray.Dataset.to_zarr` accepts the parameter `chunk_store` in 2026.7.0 but not in 2026.9.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'xarray==2026.7.0'` and `pip install 'xarray==2026.9.0'`; in each run `python check_item.py xarray.Dataset.to_zarr --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C014,breaking_change_claim,discord-py,1.7.3,2.0.0,`discord.ext.commands.Context` gained a new required parameter `view` in 2.0.0; calls valid in 1.7.3 fail. (detail: KO),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'discord-py==1.7.3'` and `pip install 'discord-py==2.0.0'`; in each run `python check_item.py discord.ext.commands.Context --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C065,breaking_change_claim,pulumi-aws,7.41.0,7.42.0,`pulumi_aws.eks.outputs.GetClusterVersionsClusterVersionResult` gained a new required parameter `control_plane_component_configs` in 7.42.0; calls valid in 7.41.0 fail. (detail: KO),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pulumi-aws==7.41.0'` and `pip install 'pulumi-aws==7.42.0'`; in each run `python check_item.py pulumi_aws.eks.outputs.GetClusterVersionsClusterVersionResult --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C122,breaking_change_claim,mypy-boto3-sqs,1.19.12,1.19.12.post1,`mypy_boto3_sqs.type_defs.SendMessageRequestQueueTypeDef` can be used in 1.19.12 but no longer exists in 1.19.12.post1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'mypy-boto3-sqs==1.19.12'` and `pip install 'mypy-boto3-sqs==1.19.12.post1'`; in each run `python check_item.py mypy_boto3_sqs.type_defs.SendMessageRequestQueueTypeDef`. Release notes, changelogs and documentation are also valid evidence." |
| C087,breaking_change_claim,apache-airflow,1.10.15,2.0.1,The parameter `destination_conn_id` of `airflow.operators.generic_transfer.GenericTransfer` can be passed positionally in 1.10.15 but only by keyword in 2.0.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'apache-airflow==1.10.15'` and `pip install 'apache-airflow==2.0.1'`; in each run `python check_item.py airflow.operators.generic_transfer.GenericTransfer --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C007,breaking_change_claim,pyhanko,0.17.2,0.18.0,`pyhanko.cli.cli` can be used in 0.17.2 but no longer exists in 0.18.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pyhanko==0.17.2'` and `pip install 'pyhanko==0.18.0'`; in each run `python check_item.py pyhanko.cli.cli`. Release notes, changelogs and documentation are also valid evidence." |
| C068,breaking_change_claim,azure-mgmt-compute,29.1.0,30.0.0,The parameter `top` of `azure.mgmt.compute.v2015_06_15.operations.VirtualMachineImagesOperations.list` can be passed positionally in 29.1.0 but only by keyword in 30.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-compute==29.1.0'` and `pip install 'azure-mgmt-compute==30.0.0'`; in each run `python check_item.py azure.mgmt.compute.v2015_06_15.operations.VirtualMachineImagesOperations.list --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C076,breaking_change_claim,peft,0.19.1,0.20.0,`peft.tuners.oft.eetq.EetqOFTLinear` gained a new required parameter `config` in 0.20.0; calls valid in 0.19.1 fail. (detail: PK),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'peft==0.19.1'` and `pip install 'peft==0.20.0'`; in each run `python check_item.py peft.tuners.oft.eetq.EetqOFTLinear --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C004,breaking_change_claim,compressed-tensors,0.15.0.1,0.16.0,`compressed_tensors.disable_offload` can be used in 0.15.0.1 but no longer exists in 0.16.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'compressed-tensors==0.15.0.1'` and `pip install 'compressed-tensors==0.16.0'`; in each run `python check_item.py compressed_tensors.disable_offload`. Release notes, changelogs and documentation are also valid evidence." |
| C095,breaking_change_claim,azure-batch,14.2.0,15.1.0,`azure.batch.models.ImageReference` can be used in 14.2.0 but no longer exists in 15.1.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-batch==14.2.0'` and `pip install 'azure-batch==15.1.0'`; in each run `python check_item.py azure.batch.models.ImageReference`. Release notes, changelogs and documentation are also valid evidence." |
| C106,breaking_change_claim,pipenv,2023.10.20,2023.10.24,`pipenv.vendor.ruamel.yaml.safe_dump_all` can be used in 2023.10.20 but no longer exists in 2023.10.24.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pipenv==2023.10.20'` and `pip install 'pipenv==2023.10.24'`; in each run `python check_item.py pipenv.vendor.ruamel.yaml.safe_dump_all`. Release notes, changelogs and documentation are also valid evidence." |
| C030,breaking_change_claim,llama-index-workflows,0.1.0,0.2.0,`workflows.utils.import_module_from_qualified_name` can be used in 0.1.0 but no longer exists in 0.2.0. (detail: still available as workflows.context.utils.import_module_from_qualified_name),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'llama-index-workflows==0.1.0'` and `pip install 'llama-index-workflows==0.2.0'`; in each run `python check_item.py workflows.utils.import_module_from_qualified_name`. Release notes, changelogs and documentation are also valid evidence." |
| P238,benchmark_pair,patsy,0.5.6,1.0.1,"This snippet works with patsy==0.5.6 and fails with patsy==1.0.1 (because of `patsy.test_highlevel.test_future`, removed): |
| from patsy.test_highlevel import test_future",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `patsy.test_highlevel.test_future`, not from the placeholder arguments." |
| C115,breaking_change_claim,azure-mgmt-cosmosdb,4.0.0,6.1.0,`azure.mgmt.cosmosdb.operations.TableResourcesOperations.migrate_table_to_autoscale` can be used in 4.0.0 but no longer exists in 6.1.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-cosmosdb==4.0.0'` and `pip install 'azure-mgmt-cosmosdb==6.1.0'`; in each run `python check_item.py azure.mgmt.cosmosdb.operations.TableResourcesOperations.migrate_table_to_autoscale`. Release notes, changelogs and documentation are also valid evidence." |
| C026,breaking_change_claim,opencv-contrib-python,3.4.15.55,3.4.16.57,`cv2.qt.plugins.platforms.libqxcb` can be used in 3.4.15.55 but no longer exists in 3.4.16.57.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'opencv-contrib-python==3.4.15.55'` and `pip install 'opencv-contrib-python==3.4.16.57'`; in each run `python check_item.py cv2.qt.plugins.platforms.libqxcb`. Release notes, changelogs and documentation are also valid evidence." |
| C129,breaking_change_claim,requests-cache,0.9.6,0.9.7,`requests_cache.cache_control.try_int` can be used in 0.9.6 but no longer exists in 0.9.7.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'requests-cache==0.9.6'` and `pip install 'requests-cache==0.9.7'`; in each run `python check_item.py requests_cache.cache_control.try_int`. Release notes, changelogs and documentation are also valid evidence." |
| C002,breaking_change_claim,robotframework,6.0.2,6.1,The parameter `error_reporter` of `robot.running.arguments.CustomArgumentConverters.from_dict` was renamed between 6.0.2 and 6.1; the old name fails in 6.1. (detail: error_reporter -> library),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'robotframework==6.0.2'` and `pip install 'robotframework==6.1'`; in each run `python check_item.py robot.running.arguments.CustomArgumentConverters.from_dict --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C034,breaking_change_claim,azure-mgmt-monitor,6.0.2,7.0.0,`azure.mgmt.monitor.v2022_10_01` can be used in 6.0.2 but no longer exists in 7.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-monitor==6.0.2'` and `pip install 'azure-mgmt-monitor==7.0.0'`; in each run `python check_item.py azure.mgmt.monitor.v2022_10_01`. Release notes, changelogs and documentation are also valid evidence." |
| C067,breaking_change_claim,pefile,2023.2.7,2024.8.26,`pefile.FILE_ALIGNMENT_HARDCODED_VALUE` can be used in 2023.2.7 but no longer exists in 2024.8.26.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pefile==2023.2.7'` and `pip install 'pefile==2024.8.26'`; in each run `python check_item.py pefile.FILE_ALIGNMENT_HARDCODED_VALUE`. Release notes, changelogs and documentation are also valid evidence." |
| C033,breaking_change_claim,etils,0.6.0,0.7.0,`etils.array_types.typing_test` can be used in 0.6.0 but no longer exists in 0.7.0. (detail: still available as etils.enp.array_types.typing_test),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'etils==0.6.0'` and `pip install 'etils==0.7.0'`; in each run `python check_item.py etils.array_types.typing_test`. Release notes, changelogs and documentation are also valid evidence." |
| C116,breaking_change_claim,sqlfluff,1.3.0,1.3.1,`sqlfluff.dialects.dialect_ansi.FileSegment` accepts the parameter `name` in 1.3.0 but not in 1.3.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'sqlfluff==1.3.0'` and `pip install 'sqlfluff==1.3.1'`; in each run `python check_item.py sqlfluff.dialects.dialect_ansi.FileSegment --signature`. Release notes, changelogs and documentation are also valid evidence." |
| P120,benchmark_pair,graphql-relay,3.1.5,3.2.0,"This snippet works with graphql-relay==3.1.5 and fails with graphql-relay==3.2.0 (because of `graphql_relay.resolve_maybe_thunk`, removed): |
| from graphql_relay import resolve_maybe_thunk",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `graphql_relay.resolve_maybe_thunk`, not from the placeholder arguments." |
| C159,breaking_change_claim,azure-mgmt-network,19.3.0,20.0.0,`azure.mgmt.network.models.SingleQueryResultDirection` can be used in 19.3.0 but no longer exists in 20.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-network==19.3.0'` and `pip install 'azure-mgmt-network==20.0.0'`; in each run `python check_item.py azure.mgmt.network.models.SingleQueryResultDirection`. Release notes, changelogs and documentation are also valid evidence." |
| C114,breaking_change_claim,ray,2.42.1,2.43.0,`ray.thirdparty_files.psutil.long` can be used in 2.42.1 but no longer exists in 2.43.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'ray==2.42.1'` and `pip install 'ray==2.43.0'`; in each run `python check_item.py ray.thirdparty_files.psutil.long`. Release notes, changelogs and documentation are also valid evidence." |
| P239,benchmark_pair,pbr,6.1.1,7.0.0,"This snippet works with pbr==6.1.1 and fails with pbr==7.0.0 (because of `pbr.packaging.NoseTest`, removed): |
| from pbr.packaging import NoseTest",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `pbr.packaging.NoseTest`, not from the placeholder arguments." |
| C131,breaking_change_claim,pybcj,0.5.3,0.6.0,`bcj.c.c_bcj` can be used in 0.5.3 but no longer exists in 0.6.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pybcj==0.5.3'` and `pip install 'pybcj==0.6.0'`; in each run `python check_item.py bcj.c.c_bcj`. Release notes, changelogs and documentation are also valid evidence." |
| P276,benchmark_pair,pymysql,1.2.0,1.2.1,"This snippet works with pymysql==1.2.0 and fails with pymysql==1.2.1 (because of `pymysql.converters.escape_bytes_prefixed`, removed): |
| from pymysql.converters import escape_bytes_prefixed",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `pymysql.converters.escape_bytes_prefixed`, not from the placeholder arguments." |
| P091,benchmark_pair,flatbuffers,25.9.23,25.12.19,"This snippet works with flatbuffers==25.9.23 and fails with flatbuffers==25.12.19 (because of `flatbuffers.builder.vtableEqual`, removed): |
| from flatbuffers.builder import vtableEqual",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `flatbuffers.builder.vtableEqual`, not from the placeholder arguments." |
| C133,breaking_change_claim,qdrant-client,1.15.1,1.16.0,`qdrant_client.models.InitFrom` can be used in 1.15.1 but no longer exists in 1.16.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'qdrant-client==1.15.1'` and `pip install 'qdrant-client==1.16.0'`; in each run `python check_item.py qdrant_client.models.InitFrom`. Release notes, changelogs and documentation are also valid evidence." |
| P233,benchmark_pair,pandas-gbq,0.29.0,0.29.1,"This snippet works with pandas-gbq==0.29.0 and fails with pandas-gbq==0.29.1 (because of `pandas_gbq.auth.CLIENT_SECRET`, removed): |
| from pandas_gbq.auth import CLIENT_SECRET",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `pandas_gbq.auth.CLIENT_SECRET`, not from the placeholder arguments." |
| P289,benchmark_pair,pytest-httpx,0.30.0,0.31.0,"This snippet works with pytest-httpx==0.30.0 and fails with pytest-httpx==0.31.0 (because of `pytest_httpx.non_mocked_hosts`, removed): |
| from pytest_httpx import non_mocked_hosts",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `pytest_httpx.non_mocked_hosts`, not from the placeholder arguments." |
| C073,breaking_change_claim,mypy-boto3-glue,1.35.3,1.35.18,`mypy_boto3_glue.type_defs.EncryptionConfigurationExtraOutputTypeDef` can be used in 1.35.3 but no longer exists in 1.35.18.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'mypy-boto3-glue==1.35.3'` and `pip install 'mypy-boto3-glue==1.35.18'`; in each run `python check_item.py mypy_boto3_glue.type_defs.EncryptionConfigurationExtraOutputTypeDef`. Release notes, changelogs and documentation are also valid evidence." |
| C048,breaking_change_claim,launchdarkly-server-sdk,7.6.1,8.0.0,`testing.impl.test_evaluator.test_variation_index_is_returned_for_bucket` can be used in 7.6.1 but no longer exists in 8.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'launchdarkly-server-sdk==7.6.1'` and `pip install 'launchdarkly-server-sdk==8.0.0'`; in each run `python check_item.py testing.impl.test_evaluator.test_variation_index_is_returned_for_bucket`. Release notes, changelogs and documentation are also valid evidence." |
| C038,breaking_change_claim,jax,0.6.0,0.6.1,`jax.experimental.shard_map.RepType` can be used in 0.6.0 but no longer exists in 0.6.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'jax==0.6.0'` and `pip install 'jax==0.6.1'`; in each run `python check_item.py jax.experimental.shard_map.RepType`. Release notes, changelogs and documentation are also valid evidence." |
| P043,benchmark_pair,cssselect,1.5.0,1.6.0,"This snippet works with cssselect==1.5.0 and fails with cssselect==1.6.0 (because of `cssselect.parser.Relation`, param_renamed `combinator`): |
| from cssselect.parser import Relation |
| Relation(selector=..., subselector=..., combinator=...)",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `cssselect.parser.Relation`, not from the placeholder arguments." |
| C001,breaking_change_claim,pydicom,2.3.1,2.4.0,`pydicom.valuerep.validate_length_and_regex` can be used in 2.3.1 but no longer exists in 2.4.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pydicom==2.3.1'` and `pip install 'pydicom==2.4.0'`; in each run `python check_item.py pydicom.valuerep.validate_length_and_regex`. Release notes, changelogs and documentation are also valid evidence." |
| C140,breaking_change_claim,propcache,0.1.0,0.2.0,`propcache.cached_property` can be used in 0.1.0 but no longer exists in 0.2.0. (detail: still available as propcache.api.cached_property),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'propcache==0.1.0'` and `pip install 'propcache==0.2.0'`; in each run `python check_item.py propcache.cached_property`. Release notes, changelogs and documentation are also valid evidence." |
| C043,breaking_change_claim,ctranslate2,3.20.0,3.21.0,`ctranslate2.specs.WhisperSpec` gained a new required parameter `num_decoder_layers` in 3.21.0; calls valid in 3.20.0 fail. (detail: PK),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'ctranslate2==3.20.0'` and `pip install 'ctranslate2==3.21.0'`; in each run `python check_item.py ctranslate2.specs.WhisperSpec --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C070,breaking_change_claim,azure-mgmt-eventhub,11.2.0,12.0.0,`azure.mgmt.eventhub.models.AuthorizationRuleListResult` can be used in 11.2.0 but no longer exists in 12.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-eventhub==11.2.0'` and `pip install 'azure-mgmt-eventhub==12.0.0'`; in each run `python check_item.py azure.mgmt.eventhub.models.AuthorizationRuleListResult`. Release notes, changelogs and documentation are also valid evidence." |
| C084,breaking_change_claim,librosa,0.8.1,0.9.0,The parameter `bins_per_octave` of `librosa.feature.chroma_cens` can be passed positionally in 0.8.1 but only by keyword in 0.9.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'librosa==0.8.1'` and `pip install 'librosa==0.9.0'`; in each run `python check_item.py librosa.feature.chroma_cens --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C152,breaking_change_claim,google-cloud-automl,1.0.3,2.2.0,The parameter `retry` of `google.cloud.automl_v1beta1.AutoMlClient.list_table_specs` can be passed positionally in 1.0.3 but only by keyword in 2.2.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'google-cloud-automl==1.0.3'` and `pip install 'google-cloud-automl==2.2.0'`; in each run `python check_item.py google.cloud.automl_v1beta1.AutoMlClient.list_table_specs --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C113,breaking_change_claim,newrelic,11.4.0,11.5.0,`newrelic.core.adaptive_sampler` can be used in 11.4.0 but no longer exists in 11.5.0. (detail: still available as newrelic.core.samplers.adaptive_sampler),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'newrelic==11.4.0'` and `pip install 'newrelic==11.5.0'`; in each run `python check_item.py newrelic.core.adaptive_sampler`. Release notes, changelogs and documentation are also valid evidence." |
| C111,breaking_change_claim,xmlschema,3.4.5,4.0.0,`xmlschema.converters.default` can be used in 3.4.5 but no longer exists in 4.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'xmlschema==3.4.5'` and `pip install 'xmlschema==4.0.0'`; in each run `python check_item.py xmlschema.converters.default`. Release notes, changelogs and documentation are also valid evidence." |
| C124,breaking_change_claim,prefect,3.6.6,3.6.7,`prefect.server.services.scheduler.RecentDeploymentsScheduler` can be used in 3.6.6 but no longer exists in 3.6.7.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'prefect==3.6.6'` and `pip install 'prefect==3.6.7'`; in each run `python check_item.py prefect.server.services.scheduler.RecentDeploymentsScheduler`. Release notes, changelogs and documentation are also valid evidence." |
| P020,benchmark_pair,catalogue,1.0.2,2.0.2,"This snippet works with catalogue==1.0.2 and fails with catalogue==2.0.2 (because of `catalogue.basestring_`, removed): |
| from catalogue import basestring_",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `catalogue.basestring_`, not from the placeholder arguments." |
| C104,breaking_change_claim,yt-dlp,2026.3.17,2026.6.9,`yt_dlp.extractor.googlepodcasts` can be used in 2026.3.17 but no longer exists in 2026.6.9.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'yt-dlp==2026.3.17'` and `pip install 'yt-dlp==2026.6.9'`; in each run `python check_item.py yt_dlp.extractor.googlepodcasts`. Release notes, changelogs and documentation are also valid evidence." |
| P322,benchmark_pair,ruamel-yaml,0.17.21,0.17.22,"This snippet works with ruamel-yaml==0.17.21 and fails with ruamel-yaml==0.17.22 (because of `ruamel.yaml.main.safe_dump_all`, removed): |
| from ruamel.yaml.main import safe_dump_all",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `ruamel.yaml.main.safe_dump_all`, not from the placeholder arguments." |
| C153,breaking_change_claim,ag-ui-protocol,0.1.22,1.0.0,`ag_ui.core.ThinkingStartEvent` can be used in 0.1.22 but no longer exists in 1.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'ag-ui-protocol==0.1.22'` and `pip install 'ag-ui-protocol==1.0.0'`; in each run `python check_item.py ag_ui.core.ThinkingStartEvent`. Release notes, changelogs and documentation are also valid evidence." |
| C080,breaking_change_claim,types-aiobotocore-s3,2.5.2.post1,2.5.2.post2,`types_aiobotocore_s3.type_defs.NotificationConfigurationFilterOutputTypeDef` can be used in 2.5.2.post1 but no longer exists in 2.5.2.post2.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'types-aiobotocore-s3==2.5.2.post1'` and `pip install 'types-aiobotocore-s3==2.5.2.post2'`; in each run `python check_item.py types_aiobotocore_s3.type_defs.NotificationConfigurationFilterOutputTypeDef`. Release notes, changelogs and documentation are also valid evidence." |
| P330,benchmark_pair,simple-websocket,0.10.1,1.0.0,"This snippet works with simple-websocket==0.10.1 and fails with simple-websocket==1.0.0 (because of `simple_websocket.Client`, param_removed `selector_class`): |
| from simple_websocket import Client |
| Client(url=..., selector_class=...)",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `simple_websocket.Client`, not from the placeholder arguments." |
| C069,breaking_change_claim,azure-mgmt-sql,3.0.1,4.0.0,`azure.mgmt.sql.models.DataWarehouseUserActivitiesListResult` can be used in 3.0.1 but no longer exists in 4.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-sql==3.0.1'` and `pip install 'azure-mgmt-sql==4.0.0'`; in each run `python check_item.py azure.mgmt.sql.models.DataWarehouseUserActivitiesListResult`. Release notes, changelogs and documentation are also valid evidence." |
| C056,breaking_change_claim,pipenv,2023.6.11,2023.6.12,`pipenv.PIPENV_ROOT` can be used in 2023.6.11 but no longer exists in 2023.6.12.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pipenv==2023.6.11'` and `pip install 'pipenv==2023.6.12'`; in each run `python check_item.py pipenv.PIPENV_ROOT`. Release notes, changelogs and documentation are also valid evidence." |
| C099,breaking_change_claim,connexion,2.15.1,3.0.0,`connexion.json_schema.default_handlers` can be used in 2.15.1 but no longer exists in 3.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'connexion==2.15.1'` and `pip install 'connexion==3.0.0'`; in each run `python check_item.py connexion.json_schema.default_handlers`. Release notes, changelogs and documentation are also valid evidence." |
| P121,benchmark_pair,graphviz,0.18,0.18.1,"This snippet works with graphviz==0.18 and fails with graphviz==0.18.1 (because of `graphviz.backend.FORMATTERS`, removed): |
| from graphviz.backend import FORMATTERS",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `graphviz.backend.FORMATTERS`, not from the placeholder arguments." |
| C091,breaking_change_claim,azure-mgmt-trafficmanager,1.1.0,2.0.0,`azure.mgmt.trafficmanager.models.ProfileListResult` can be used in 1.1.0 but no longer exists in 2.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-trafficmanager==1.1.0'` and `pip install 'azure-mgmt-trafficmanager==2.0.0'`; in each run `python check_item.py azure.mgmt.trafficmanager.models.ProfileListResult`. Release notes, changelogs and documentation are also valid evidence." |
| P262,benchmark_pair,pycparser,2.23,3.0,"This snippet works with pycparser==2.23 and fails with pycparser==3.0 (because of `pycparser.c_parser.CParser.p_block_item_list`, removed): |
| from pycparser.c_parser import CParser |
| CParser.p_block_item_list",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `pycparser.c_parser.CParser.p_block_item_list`, not from the placeholder arguments." |
| C036,breaking_change_claim,ezdxf,0.17.1,0.17.2,`ezdxf.sections.table.UCSTable` accepts the parameter `doc` in 0.17.1 but not in 0.17.2.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'ezdxf==0.17.1'` and `pip install 'ezdxf==0.17.2'`; in each run `python check_item.py ezdxf.sections.table.UCSTable --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C052,breaking_change_claim,azure-mgmt-authorization,3.0.0,4.0.0,`azure.mgmt.authorization.v2021_12_01_preview.aio.operations.AlertDefinitionsOperations` can be used in 3.0.0 but no longer exists in 4.0.0. (detail: still available as azure.mgmt.authorization.v2022_08_01_preview.operations.AlertDefinitionsOperations),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-authorization==3.0.0'` and `pip install 'azure-mgmt-authorization==4.0.0'`; in each run `python check_item.py azure.mgmt.authorization.v2021_12_01_preview.aio.operations.AlertDefinitionsOperations`. Release notes, changelogs and documentation are also valid evidence." |
| C092,breaking_change_claim,pyrate-limiter,2.10.0,3.0.0,`pyrate_limiter.SQLITE_MAX_VARIABLE_NUMBER` can be used in 2.10.0 but no longer exists in 3.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pyrate-limiter==2.10.0'` and `pip install 'pyrate-limiter==3.0.0'`; in each run `python check_item.py pyrate_limiter.SQLITE_MAX_VARIABLE_NUMBER`. Release notes, changelogs and documentation are also valid evidence." |
| C156,breaking_change_claim,bokeh,3.3.4,3.4.0,`bokeh.models.Divider` can be used in 3.3.4 but no longer exists in 3.4.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'bokeh==3.3.4'` and `pip install 'bokeh==3.4.0'`; in each run `python check_item.py bokeh.models.Divider`. Release notes, changelogs and documentation are also valid evidence." |
| C011,breaking_change_claim,azure-mgmt-cdn,13.1.1,14.0.0,`azure.mgmt.cdn.models.CookiesMatchConditionParametersTypeName` can be used in 13.1.1 but no longer exists in 14.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-cdn==13.1.1'` and `pip install 'azure-mgmt-cdn==14.0.0'`; in each run `python check_item.py azure.mgmt.cdn.models.CookiesMatchConditionParametersTypeName`. Release notes, changelogs and documentation are also valid evidence." |
| C101,breaking_change_claim,browser-use,0.4.5,0.5.0,`browser_use.config.Config.NOVITA_API_KEY` can be used in 0.4.5 but no longer exists in 0.5.0. (detail: still available as browser_use.config.OldConfig.NOVITA_API_KEY),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'browser-use==0.4.5'` and `pip install 'browser-use==0.5.0'`; in each run `python check_item.py browser_use.config.Config.NOVITA_API_KEY`. Release notes, changelogs and documentation are also valid evidence." |
| C071,breaking_change_claim,mypy-boto3-cloudformation,1.35.64,1.35.93,`mypy_boto3_cloudformation.type_defs.DescribeStacksInputStackCreateCompleteWaitTypeDef` can be used in 1.35.64 but no longer exists in 1.35.93.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'mypy-boto3-cloudformation==1.35.64'` and `pip install 'mypy-boto3-cloudformation==1.35.93'`; in each run `python check_item.py mypy_boto3_cloudformation.type_defs.DescribeStacksInputStackCreateCompleteWaitTypeDef`. Release notes, changelogs and documentation are also valid evidence." |
| C051,breaking_change_claim,librosa,0.11.0,1.0.0,`librosa.set_fftlib` can be used in 0.11.0 but no longer exists in 1.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'librosa==0.11.0'` and `pip install 'librosa==1.0.0'`; in each run `python check_item.py librosa.set_fftlib`. Release notes, changelogs and documentation are also valid evidence." |
| P048,benchmark_pair,datadog,0.53.0,0.54.0,"This snippet works with datadog==0.53.0 and fails with datadog==0.54.0 (because of `datadog.DogStatsd`, param_removed `socket_connect_timeout`): |
| from datadog import DogStatsd |
| DogStatsd(socket_connect_timeout=...)",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `datadog.DogStatsd`, not from the placeholder arguments." |
| C146,breaking_change_claim,pypandoc,1.7.2,1.8.1,`pypandoc.convert` can be used in 1.7.2 but no longer exists in 1.8.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pypandoc==1.7.2'` and `pip install 'pypandoc==1.8.1'`; in each run `python check_item.py pypandoc.convert`. Release notes, changelogs and documentation are also valid evidence." |
| C085,breaking_change_claim,funcy,1.18,2.0,`funcy.PY2` can be used in 1.18 but no longer exists in 2.0. (detail: still available as funcy.compat.PY2),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'funcy==1.18'` and `pip install 'funcy==2.0'`; in each run `python check_item.py funcy.PY2`. Release notes, changelogs and documentation are also valid evidence." |
| C028,breaking_change_claim,azure-ai-projects,2.1.0,2.2.0,`azure.ai.projects.models.AgentEndpoint` can be used in 2.1.0 but no longer exists in 2.2.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-ai-projects==2.1.0'` and `pip install 'azure-ai-projects==2.2.0'`; in each run `python check_item.py azure.ai.projects.models.AgentEndpoint`. Release notes, changelogs and documentation are also valid evidence." |
| C136,breaking_change_claim,trafilatura,1.8.1,1.9.0,`trafilatura.core.handle_formatting` can be used in 1.8.1 but no longer exists in 1.9.0. (detail: still available as trafilatura.main_extractor.handle_formatting),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'trafilatura==1.8.1'` and `pip install 'trafilatura==1.9.0'`; in each run `python check_item.py trafilatura.core.handle_formatting`. Release notes, changelogs and documentation are also valid evidence." |
| C100,breaking_change_claim,azure-mgmt-batch,17.3.0,18.0.0,`azure.mgmt.batch.models.CloudServiceConfiguration` can be used in 17.3.0 but no longer exists in 18.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-batch==17.3.0'` and `pip install 'azure-mgmt-batch==18.0.0'`; in each run `python check_item.py azure.mgmt.batch.models.CloudServiceConfiguration`. Release notes, changelogs and documentation are also valid evidence." |
| P101,benchmark_pair,google-cloud-bigquery,2.34.4,3.0.1,"This snippet works with google-cloud-bigquery==2.34.4 and fails with google-cloud-bigquery==3.0.1 (because of `google.cloud.bigquery.LegacyBigQueryStorageError`, removed): |
| from google.cloud.bigquery import LegacyBigQueryStorageError",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `google.cloud.bigquery.LegacyBigQueryStorageError`, not from the placeholder arguments." |
| C119,breaking_change_claim,azure-mgmt-cognitiveservices,13.7.0,14.0.0,`azure.mgmt.cognitiveservices.models.NetworkInjections` can be used in 13.7.0 but no longer exists in 14.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-cognitiveservices==13.7.0'` and `pip install 'azure-mgmt-cognitiveservices==14.0.0'`; in each run `python check_item.py azure.mgmt.cognitiveservices.models.NetworkInjections`. Release notes, changelogs and documentation are also valid evidence." |
| C046,breaking_change_claim,workos,10.3.0,10.4.0,`workos.common.models.WaitlistUserStateLiteral` can be used in 10.3.0 but no longer exists in 10.4.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'workos==10.3.0'` and `pip install 'workos==10.4.0'`; in each run `python check_item.py workos.common.models.WaitlistUserStateLiteral`. Release notes, changelogs and documentation are also valid evidence." |
| C060,breaking_change_claim,pytorch-lightning,1.7.7,1.8.0,The parameter `stage` of `pytorch_lightning.LightningModule.teardown` has a default in 1.7.7 but is required in 1.8.0. (detail: was None),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pytorch-lightning==1.7.7'` and `pip install 'pytorch-lightning==1.8.0'`; in each run `python check_item.py pytorch_lightning.LightningModule.teardown --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C003,breaking_change_claim,azure-mgmt-servicebus,9.0.0,10.0.0,`azure.mgmt.servicebus.models.SBQueueListResult` can be used in 9.0.0 but no longer exists in 10.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-servicebus==9.0.0'` and `pip install 'azure-mgmt-servicebus==10.0.0'`; in each run `python check_item.py azure.mgmt.servicebus.models.SBQueueListResult`. Release notes, changelogs and documentation are also valid evidence." |
| C107,breaking_change_claim,ray,2.40.0,2.41.0,`ray.util.state.state_manager.StateDataSourceClient.get_task_info` can be used in 2.40.0 but no longer exists in 2.41.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'ray==2.40.0'` and `pip install 'ray==2.41.0'`; in each run `python check_item.py ray.util.state.state_manager.StateDataSourceClient.get_task_info`. Release notes, changelogs and documentation are also valid evidence." |
| C050,breaking_change_claim,apprise,1.7.6,1.8.0,`apprise.plugins.NotifyNotica` can be used in 1.7.6 but no longer exists in 1.8.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'apprise==1.7.6'` and `pip install 'apprise==1.8.0'`; in each run `python check_item.py apprise.plugins.NotifyNotica`. Release notes, changelogs and documentation are also valid evidence." |
| C125,breaking_change_claim,azure-ai-agents,1.0.2,1.1.0,`azure.ai.agents.operations.AgentsClientOperationsMixin` can be used in 1.0.2 but no longer exists in 1.1.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-ai-agents==1.0.2'` and `pip install 'azure-ai-agents==1.1.0'`; in each run `python check_item.py azure.ai.agents.operations.AgentsClientOperationsMixin`. Release notes, changelogs and documentation are also valid evidence." |
| C126,breaking_change_claim,pandera,0.20.3,0.20.4,`pandera.engines.pandas_engine.GEOPANDAS_INSTALLED` can be used in 0.20.3 but no longer exists in 0.20.4. (detail: still available as pandera.typing.geopandas.GEOPANDAS_INSTALLED),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pandera==0.20.3'` and `pip install 'pandera==0.20.4'`; in each run `python check_item.py pandera.engines.pandas_engine.GEOPANDAS_INSTALLED`. Release notes, changelogs and documentation are also valid evidence." |
| P202,benchmark_pair,msal,1.21.0,1.22.0,"This snippet works with msal==1.21.0 and fails with msal==1.22.0 (because of `msal.authority.canonicalize`, param_renamed `authority_url`): |
| from msal.authority import canonicalize |
| canonicalize(authority_url=...)",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `msal.authority.canonicalize`, not from the placeholder arguments." |
| P251,benchmark_pair,pkginfo,1.11.0,1.11.1,"This snippet works with pkginfo==1.11.0 and fails with pkginfo==1.11.1 (because of `pkginfo.commandline.ParsedOptions`, removed): |
| from pkginfo.commandline import ParsedOptions",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `pkginfo.commandline.ParsedOptions`, not from the placeholder arguments." |
| C040,breaking_change_claim,discord-py,1.7.3,2.0.0,`discord.Relationship` can be used in 1.7.3 but no longer exists in 2.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'discord-py==1.7.3'` and `pip install 'discord-py==2.0.0'`; in each run `python check_item.py discord.Relationship`. Release notes, changelogs and documentation are also valid evidence." |
| C008,breaking_change_claim,rdkit,2022.3.5,2022.9.1,`rdkit.Chem.PandasTools.patchPandasrepr` can be used in 2022.3.5 but no longer exists in 2022.9.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'rdkit==2022.3.5'` and `pip install 'rdkit==2022.9.1'`; in each run `python check_item.py rdkit.Chem.PandasTools.patchPandasrepr`. Release notes, changelogs and documentation are also valid evidence." |
| C118,breaking_change_claim,keras,3.12.4,3.13.0,`keras.src.layers.preprocessing.image_preprocessing.solarization_test` can be used in 3.12.4 but no longer exists in 3.13.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'keras==3.12.4'` and `pip install 'keras==3.13.0'`; in each run `python check_item.py keras.src.layers.preprocessing.image_preprocessing.solarization_test`. Release notes, changelogs and documentation are also valid evidence." |
| P312,benchmark_pair,pywin32,307,308,"This snippet works with pywin32==307 and fails with pywin32==308 (because of `win32.scripts.VersionStamp.bulkstamp.walk`, param_renamed `arg`): |
| from win32.scripts.VersionStamp.bulkstamp import walk |
| walk(dirname=..., names=..., arg=...)",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `win32.scripts.VersionStamp.bulkstamp.walk`, not from the placeholder arguments." |
| C090,breaking_change_claim,tensorflow,2.2.3,2.3.2,`tensorflow.python.data.experimental.ops.snapshot.snapshot` accepts the parameter `pending_snapshot_expiry_seconds` in 2.2.3 but not in 2.3.2.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'tensorflow==2.2.3'` and `pip install 'tensorflow==2.3.2'`; in each run `python check_item.py tensorflow.python.data.experimental.ops.snapshot.snapshot --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C061,breaking_change_claim,azure-monitor-query,1.4.1,2.0.0,`azure.monitor.query.TimeSeriesElement` can be used in 1.4.1 but no longer exists in 2.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-monitor-query==1.4.1'` and `pip install 'azure-monitor-query==2.0.0'`; in each run `python check_item.py azure.monitor.query.TimeSeriesElement`. Release notes, changelogs and documentation are also valid evidence." |
| P382,benchmark_pair,watchdog,4.0.2,5.0.0,"This snippet works with watchdog==4.0.2 and fails with watchdog==5.0.0 (because of `watchdog.observers.winapi.FILE_NOTIFY_INFORMATION`, removed): |
| from watchdog.observers.winapi import FILE_NOTIFY_INFORMATION",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `watchdog.observers.winapi.FILE_NOTIFY_INFORMATION`, not from the placeholder arguments." |
| P108,benchmark_pair,google-cloud-logging,1.15.3,2.1.0,"This snippet works with google-cloud-logging==1.15.3 and fails with google-cloud-logging==2.1.0 (because of `google.cloud.logging_v2.MetricsServiceV2Client`, removed): |
| from google.cloud.logging_v2 import MetricsServiceV2Client",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `google.cloud.logging_v2.MetricsServiceV2Client`, not from the placeholder arguments." |
| C009,breaking_change_claim,apache-airflow-providers-google,16.1.0,17.0.0,"The positional parameters of `airflow.providers.google.cloud.triggers.kubernetes_engine.GKEJobTrigger` were reordered between 16.1.0 and 17.0.0. (detail: ['cluster_url', 'ssl_ca_cert', 'job_name', 'job_namespace', 'pod_name', 'pod_namespace', 'base_container_name', 'gcp_conn_id', 'poll_interval', 'impersonation_chain', 'get_logs', 'do_xcom_push'] -> ['cluster_url', 'ssl_ca_cert', 'job_name', 'job_namespace', 'pod_namespace', 'base_container_name', 'pod_name', 'gcp_conn_id', 'poll_interval', 'impersonation_chain', 'get_logs', 'do_xcom_push'])",Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'apache-airflow-providers-google==16.1.0'` and `pip install 'apache-airflow-providers-google==17.0.0'`; in each run `python check_item.py airflow.providers.google.cloud.triggers.kubernetes_engine.GKEJobTrigger --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C059,breaking_change_claim,exa-py,1.14.1,1.14.2,`exa_py.websets.core.Stream` can be used in 1.14.1 but no longer exists in 1.14.2.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'exa-py==1.14.1'` and `pip install 'exa-py==1.14.2'`; in each run `python check_item.py exa_py.websets.core.Stream`. Release notes, changelogs and documentation are also valid evidence." |
| P350,benchmark_pair,terminado,0.9.5,0.10.0,"This snippet works with terminado==0.9.5 and fails with terminado==0.10.0 (because of `terminado.management.byte_code`, removed): |
| from terminado.management import byte_code",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `terminado.management.byte_code`, not from the placeholder arguments." |
| C134,breaking_change_claim,azure-mgmt-compute,35.0.0,36.0.0,`azure.mgmt.compute.v2022_09_04` can be used in 35.0.0 but no longer exists in 36.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-compute==35.0.0'` and `pip install 'azure-mgmt-compute==36.0.0'`; in each run `python check_item.py azure.mgmt.compute.v2022_09_04`. Release notes, changelogs and documentation are also valid evidence." |
| P326,benchmark_pair,secretstorage,3.4.1,3.5.0,"This snippet works with secretstorage==3.4.1 and fails with secretstorage==3.5.0 (because of `secretstorage.dhcrypto.int_to_bytes`, removed): |
| from secretstorage.dhcrypto import int_to_bytes",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `secretstorage.dhcrypto.int_to_bytes`, not from the placeholder arguments." |
| C045,breaking_change_claim,minio,7.2.19,7.2.20,`minio.Minio.append_object` accepts the parameter `filename` in 7.2.19 but not in 7.2.20.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'minio==7.2.19'` and `pip install 'minio==7.2.20'`; in each run `python check_item.py minio.Minio.append_object --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C089,breaking_change_claim,ortools,9.14.6206,9.15.6755,`ortools.constraint_solver.pywrapcp.GlobalVehicleBreaksConstraint` can be used in 9.14.6206 but no longer exists in 9.15.6755.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'ortools==9.14.6206'` and `pip install 'ortools==9.15.6755'`; in each run `python check_item.py ortools.constraint_solver.pywrapcp.GlobalVehicleBreaksConstraint`. Release notes, changelogs and documentation are also valid evidence." |
| C151,breaking_change_claim,harbor-rewardkit,0.1.7,0.2.0,`rewardkit.agents.ClaudeCodeCLI` can be used in 0.1.7 but no longer exists in 0.2.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'harbor-rewardkit==0.1.7'` and `pip install 'harbor-rewardkit==0.2.0'`; in each run `python check_item.py rewardkit.agents.ClaudeCodeCLI`. Release notes, changelogs and documentation are also valid evidence." |
| C041,breaking_change_claim,ezdxf,0.15.2,0.16,`ezdxf.math.rational_spline_from_ellipse` can be used in 0.15.2 but no longer exists in 0.16.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'ezdxf==0.15.2'` and `pip install 'ezdxf==0.16'`; in each run `python check_item.py ezdxf.math.rational_spline_from_ellipse`. Release notes, changelogs and documentation are also valid evidence." |
| C105,breaking_change_claim,motor,2.5.1,3.0.0,`motor.core.get_default_database_doc` can be used in 2.5.1 but no longer exists in 3.0.0. (detail: still available as motor.docstrings.get_default_database_doc),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'motor==2.5.1'` and `pip install 'motor==3.0.0'`; in each run `python check_item.py motor.core.get_default_database_doc`. Release notes, changelogs and documentation are also valid evidence." |
| P379,benchmark_pair,vcs-versioning,1.1.1,2.0.1,"This snippet works with vcs-versioning==1.1.1 and fails with vcs-versioning==2.0.1 (because of `vcs_versioning.overrides.source_epoch_or_utc_now`, removed): |
| from vcs_versioning.overrides import source_epoch_or_utc_now",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `vcs_versioning.overrides.source_epoch_or_utc_now`, not from the placeholder arguments." |
| C074,breaking_change_claim,azure-mgmt-containerservice,33.0.0,34.0.0,`azure.mgmt.containerservice.models.ManualScaleProfile` can be used in 33.0.0 but no longer exists in 34.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-containerservice==33.0.0'` and `pip install 'azure-mgmt-containerservice==34.0.0'`; in each run `python check_item.py azure.mgmt.containerservice.models.ManualScaleProfile`. Release notes, changelogs and documentation are also valid evidence." |
| C072,breaking_change_claim,metricflow,0.140.0,0.200.0,`metricflow.errors.errors.ParsingException` can be used in 0.140.0 but no longer exists in 0.200.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'metricflow==0.140.0'` and `pip install 'metricflow==0.200.0'`; in each run `python check_item.py metricflow.errors.errors.ParsingException`. Release notes, changelogs and documentation are also valid evidence." |
| C098,breaking_change_claim,reductoai,0.12.0,0.13.0,`reducto.types.shared_params.ChunkingConfig` can be used in 0.12.0 but no longer exists in 0.13.0. (detail: still available as reducto.types.ChunkingConfig),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'reductoai==0.12.0'` and `pip install 'reductoai==0.13.0'`; in each run `python check_item.py reducto.types.shared_params.ChunkingConfig`. Release notes, changelogs and documentation are also valid evidence." |
| C123,breaking_change_claim,azure-mgmt-billing,7.0.0,8.0.0,`azure.mgmt.billing.models.ProductListResult` can be used in 7.0.0 but no longer exists in 8.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-billing==7.0.0'` and `pip install 'azure-mgmt-billing==8.0.0'`; in each run `python check_item.py azure.mgmt.billing.models.ProductListResult`. Release notes, changelogs and documentation are also valid evidence." |
| C086,breaking_change_claim,pyairtable,1.5.0,2.0.0,The parameter `model` of `pyairtable.orm.fields.LookupField` was renamed between 1.5.0 and 2.0.0; the old name fails in 2.0.0. (detail: model -> validate_type),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pyairtable==1.5.0'` and `pip install 'pyairtable==2.0.0'`; in each run `python check_item.py pyairtable.orm.fields.LookupField --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C006,breaking_change_claim,timm,0.5.4,0.6.5,`timm.models.CspNet` accepts the parameter `aa_layer` in 0.5.4 but not in 0.6.5.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'timm==0.5.4'` and `pip install 'timm==0.6.5'`; in each run `python check_item.py timm.models.CspNet --signature`. Release notes, changelogs and documentation are also valid evidence." |
| P232,benchmark_pair,pandas-gbq,0.17.9,0.18.0,"This snippet works with pandas-gbq==0.17.9 and fails with pandas-gbq==0.18.0 (because of `pandas_gbq.gbq.InvalidSchema`, param_removed `remote_schema`): |
| from pandas_gbq.gbq import InvalidSchema |
| InvalidSchema(message=..., local_schema=..., remote_schema=...)",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `pandas_gbq.gbq.InvalidSchema`, not from the placeholder arguments." |
| C132,breaking_change_claim,azure-mgmt-billing,7.0.0,8.0.0,`azure.mgmt.billing.models.Reservation.benefit_start_time` can be used in 7.0.0 but no longer exists in 8.0.0. (detail: still available as azure.mgmt.billing.models.ReservationOrder.benefit_start_time),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-billing==7.0.0'` and `pip install 'azure-mgmt-billing==8.0.0'`; in each run `python check_item.py azure.mgmt.billing.models.Reservation.benefit_start_time`. Release notes, changelogs and documentation are also valid evidence." |
| C020,breaking_change_claim,pint,0.18,0.20,`pint.testsuite.test_compat_downcast.test_array_quantity_creation_by_multiplication` gained a new required parameter `local_registry` in 0.20; calls valid in 0.18 fail. (detail: PK),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pint==0.18'` and `pip install 'pint==0.20'`; in each run `python check_item.py pint.testsuite.test_compat_downcast.test_array_quantity_creation_by_multiplication --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C044,breaking_change_claim,multimethod,1.12,2.0,`multimethod.overload` can be used in 1.12 but no longer exists in 2.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'multimethod==1.12'` and `pip install 'multimethod==2.0'`; in each run `python check_item.py multimethod.overload`. Release notes, changelogs and documentation are also valid evidence." |
| C097,breaking_change_claim,azure-synapse-artifacts,0.12.0,0.13.0,`azure.synapse.artifacts.models.CloudErrorAutoGenerated` can be used in 0.12.0 but no longer exists in 0.13.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-synapse-artifacts==0.12.0'` and `pip install 'azure-synapse-artifacts==0.13.0'`; in each run `python check_item.py azure.synapse.artifacts.models.CloudErrorAutoGenerated`. Release notes, changelogs and documentation are also valid evidence." |
| C022,breaking_change_claim,lmnr,0.7.41,0.7.42,`lmnr.opentelemetry_lib.opentelemetry.instrumentation.anthropic.WrappedAsyncMessageStreamManager` accepts the parameter `token_histogram` in 0.7.41 but not in 0.7.42.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'lmnr==0.7.41'` and `pip install 'lmnr==0.7.42'`; in each run `python check_item.py lmnr.opentelemetry_lib.opentelemetry.instrumentation.anthropic.WrappedAsyncMessageStreamManager --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C054,breaking_change_claim,pygit2,1.13.3,1.14.0,`pygit2.GIT_DIFF_FIND_ALL` can be used in 1.13.3 but no longer exists in 1.14.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pygit2==1.13.3'` and `pip install 'pygit2==1.14.0'`; in each run `python check_item.py pygit2.GIT_DIFF_FIND_ALL`. Release notes, changelogs and documentation are also valid evidence." |
| C066,breaking_change_claim,azure-mgmt-datafactory,9.3.0,10.0.0,`azure.mgmt.datafactory.models.SqlPartitionOption` can be used in 9.3.0 but no longer exists in 10.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-datafactory==9.3.0'` and `pip install 'azure-mgmt-datafactory==10.0.0'`; in each run `python check_item.py azure.mgmt.datafactory.models.SqlPartitionOption`. Release notes, changelogs and documentation are also valid evidence." |
| C155,breaking_change_claim,azure-mgmt-recoveryservicesbackup,10.0.0,11.0.0,The parameter `filter` of `azure.mgmt.recoveryservicesbackup.operations.DeletedProtectionContainersOperations.list` can be passed positionally in 10.0.0 but only by keyword in 11.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-recoveryservicesbackup==10.0.0'` and `pip install 'azure-mgmt-recoveryservicesbackup==11.0.0'`; in each run `python check_item.py azure.mgmt.recoveryservicesbackup.operations.DeletedProtectionContainersOperations.list --signature`. Release notes, changelogs and documentation are also valid evidence." |
| P115,benchmark_pair,google-cloud-storage,3.4.0,3.4.1,"This snippet works with google-cloud-storage==3.4.0 and fails with google-cloud-storage==3.4.1 (because of `google.cloud.storage.Blob`, param_removed `crc32c_checksum`): |
| from google.cloud.storage import Blob |
| Blob(name=..., bucket=..., crc32c_checksum=...)",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `google.cloud.storage.Blob`, not from the placeholder arguments." |
| C078,breaking_change_claim,jax,0.4.16,0.4.17,`jax.numpy.typing` can be used in 0.4.16 but no longer exists in 0.4.17.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'jax==0.4.16'` and `pip install 'jax==0.4.17'`; in each run `python check_item.py jax.numpy.typing`. Release notes, changelogs and documentation are also valid evidence." |
| C160,breaking_change_claim,workos,5.46.0,6.0.0,`workos.types.events.FlagRuleUpdatedEvent` can be used in 5.46.0 but no longer exists in 6.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'workos==5.46.0'` and `pip install 'workos==6.0.0'`; in each run `python check_item.py workos.types.events.FlagRuleUpdatedEvent`. Release notes, changelogs and documentation are also valid evidence." |
| P136,benchmark_pair,inflect,6.2.0,7.0.0,"This snippet works with inflect==6.2.0 and fails with inflect==7.0.0 (because of `inflect.print3`, removed): |
| from inflect import print3",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `inflect.print3`, not from the placeholder arguments." |
| P075,benchmark_pair,envier,0.3.0,0.4.0,"This snippet works with envier==0.3.0 and fails with envier==0.4.0 (because of `envier.sphinx.RST_PARSER_SETTINGS`, removed): |
| from envier.sphinx import RST_PARSER_SETTINGS",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `envier.sphinx.RST_PARSER_SETTINGS`, not from the placeholder arguments." |
| C088,breaking_change_claim,mkdocstrings-python,1.6.2,1.6.3,The parameter `config_file_path` of `mkdocstrings_handlers.python.get_handler` can be passed positionally in 1.6.2 but only by keyword in 1.6.3.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'mkdocstrings-python==1.6.2'` and `pip install 'mkdocstrings-python==1.6.3'`; in each run `python check_item.py mkdocstrings_handlers.python.get_handler --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C127,breaking_change_claim,onnx,1.10.2,1.11.0,`onnx.string_types` can be used in 1.10.2 but no longer exists in 1.11.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'onnx==1.10.2'` and `pip install 'onnx==1.11.0'`; in each run `python check_item.py onnx.string_types`. Release notes, changelogs and documentation are also valid evidence." |
| C135,breaking_change_claim,azure-mgmt-servicefabric,2.0.0,2.1.0,`azure.mgmt.servicefabric.models.Enum14` can be used in 2.0.0 but no longer exists in 2.1.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-servicefabric==2.0.0'` and `pip install 'azure-mgmt-servicefabric==2.1.0'`; in each run `python check_item.py azure.mgmt.servicefabric.models.Enum14`. Release notes, changelogs and documentation are also valid evidence." |
| C021,breaking_change_claim,mkdocstrings,0.14.0,0.15.0,`mkdocstrings.references` can be used in 0.14.0 but no longer exists in 0.15.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'mkdocstrings==0.14.0'` and `pip install 'mkdocstrings==0.15.0'`; in each run `python check_item.py mkdocstrings.references`. Release notes, changelogs and documentation are also valid evidence." |
| C063,breaking_change_claim,autopep8,2.0.4,2.1.0,`autopep8.fix_2to3` can be used in 2.0.4 but no longer exists in 2.1.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'autopep8==2.0.4'` and `pip install 'autopep8==2.1.0'`; in each run `python check_item.py autopep8.fix_2to3`. Release notes, changelogs and documentation are also valid evidence." |
| C154,breaking_change_claim,py7zr,0.22.0,1.0.0,`py7zr.helpers.BufferOverflow` can be used in 0.22.0 but no longer exists in 1.0.0. (detail: still available as py7zr.io.BufferOverflow),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'py7zr==0.22.0'` and `pip install 'py7zr==1.0.0'`; in each run `python check_item.py py7zr.helpers.BufferOverflow`. Release notes, changelogs and documentation are also valid evidence." |
| C064,breaking_change_claim,flask-caching,1.10.1,1.11.0,`flask_caching.BaseCache.get` can be used in 1.10.1 but no longer exists in 1.11.0. (detail: still available as flask_caching.Cache.get),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'flask-caching==1.10.1'` and `pip install 'flask-caching==1.11.0'`; in each run `python check_item.py flask_caching.BaseCache.get`. Release notes, changelogs and documentation are also valid evidence." |
| C077,breaking_change_claim,azure-mgmt-cosmosdb,9.5.0,9.5.1,`azure.mgmt.cosmosdb.models.DataTransferServiceResourceCreateUpdateParameters` can be used in 9.5.0 but no longer exists in 9.5.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-cosmosdb==9.5.0'` and `pip install 'azure-mgmt-cosmosdb==9.5.1'`; in each run `python check_item.py azure.mgmt.cosmosdb.models.DataTransferServiceResourceCreateUpdateParameters`. Release notes, changelogs and documentation are also valid evidence." |
| C093,breaking_change_claim,azure-mgmt-recoveryservicesbackup,10.0.0,11.0.0,`azure.mgmt.recoveryservicesbackup.models.BMSBackupEnginesQueryObject` can be used in 10.0.0 but no longer exists in 11.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-recoveryservicesbackup==10.0.0'` and `pip install 'azure-mgmt-recoveryservicesbackup==11.0.0'`; in each run `python check_item.py azure.mgmt.recoveryservicesbackup.models.BMSBackupEnginesQueryObject`. Release notes, changelogs and documentation are also valid evidence." |
| C117,breaking_change_claim,diffusers,0.21.4,0.22.0,The parameter `noise` of `diffusers.schedulers.DPMSolverMultistepScheduler.dpm_solver_first_order_update` can be passed positionally in 0.21.4 but only by keyword in 0.22.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'diffusers==0.21.4'` and `pip install 'diffusers==0.22.0'`; in each run `python check_item.py diffusers.schedulers.DPMSolverMultistepScheduler.dpm_solver_first_order_update --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C120,breaking_change_claim,html-to-markdown,3.4.0,3.5.0,`html_to_markdown.NodeType.TableFoot` can be used in 3.4.0 but no longer exists in 3.5.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'html-to-markdown==3.4.0'` and `pip install 'html-to-markdown==3.5.0'`; in each run `python check_item.py html_to_markdown.NodeType.TableFoot`. Release notes, changelogs and documentation are also valid evidence." |
| C081,breaking_change_claim,meson,0.63.3,0.64.0,`mesonbuild.compilers.DmdDCompiler` can be used in 0.63.3 but no longer exists in 0.64.0. (detail: still available as mesonbuild.compilers.d.DmdDCompiler),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'meson==0.63.3'` and `pip install 'meson==0.64.0'`; in each run `python check_item.py mesonbuild.compilers.DmdDCompiler`. Release notes, changelogs and documentation are also valid evidence." |
| C110,breaking_change_claim,faiss-cpu,1.13.2,1.14.2,`faiss.swigfaiss.RaBitQStats` can be used in 1.13.2 but no longer exists in 1.14.2. (detail: still available as faiss.RaBitQStats),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'faiss-cpu==1.13.2'` and `pip install 'faiss-cpu==1.14.2'`; in each run `python check_item.py faiss.swigfaiss.RaBitQStats`. Release notes, changelogs and documentation are also valid evidence." |
| C137,breaking_change_claim,dlt,0.5.4,1.0.0,`dlt.destinations.impl.lancedb.models` can be used in 0.5.4 but no longer exists in 1.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'dlt==0.5.4'` and `pip install 'dlt==1.0.0'`; in each run `python check_item.py dlt.destinations.impl.lancedb.models`. Release notes, changelogs and documentation are also valid evidence." |
| C128,breaking_change_claim,google-analytics-admin,0.24.1,0.25.0,`google.analytics.admin_v1alpha.services.analytics_admin_service.transports.AnalyticsAdminServiceGrpcAsyncIOTransport.set_automated_ga4_configuration_opt_out` can be used in 0.24.1 but no longer exists in 0.25.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'google-analytics-admin==0.24.1'` and `pip install 'google-analytics-admin==0.25.0'`; in each run `python check_item.py google.analytics.admin_v1alpha.services.analytics_admin_service.transports.AnalyticsAdminServiceGrpcAsyncIOTransport.set_automated_ga4_configuration_opt_out`. Release notes, changelogs and documentation are also valid evidence." |
| C053,breaking_change_claim,choreographer,0.99.7,1.0.3,`choreographer.Browser.run_output_thread` can be used in 0.99.7 but no longer exists in 1.0.3.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'choreographer==0.99.7'` and `pip install 'choreographer==1.0.3'`; in each run `python check_item.py choreographer.Browser.run_output_thread`. Release notes, changelogs and documentation are also valid evidence." |
| P252,benchmark_pair,platformdirs,4.9.4,4.9.6,"This snippet works with platformdirs==4.9.4 and fails with platformdirs==4.9.6 (because of `platformdirs.version.TYPE_CHECKING`, removed): |
| from platformdirs.version import TYPE_CHECKING",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `platformdirs.version.TYPE_CHECKING`, not from the placeholder arguments." |
| P178,benchmark_pair,linkify-it-py,1.0.3,2.0.0,"This snippet works with linkify-it-py==1.0.3 and fails with linkify-it-py==2.0.0 (because of `linkify_it.ucre.SRC_HOST_TERMINATOR`, removed): |
| from linkify_it.ucre import SRC_HOST_TERMINATOR",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `linkify_it.ucre.SRC_HOST_TERMINATOR`, not from the placeholder arguments." |
| C017,breaking_change_claim,xmlschema,1.8.0,1.8.1,`xmlschema.resources.NormalizedLocationsType` can be used in 1.8.0 but no longer exists in 1.8.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'xmlschema==1.8.0'` and `pip install 'xmlschema==1.8.1'`; in each run `python check_item.py xmlschema.resources.NormalizedLocationsType`. Release notes, changelogs and documentation are also valid evidence." |
| C141,breaking_change_claim,dspy,2.5.43,2.6.0,`dspy.PremAI` can be used in 2.5.43 but no longer exists in 2.6.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'dspy==2.5.43'` and `pip install 'dspy==2.6.0'`; in each run `python check_item.py dspy.PremAI`. Release notes, changelogs and documentation are also valid evidence." |
| P394,benchmark_pair,yamllint,1.33.0,1.34.0,"This snippet works with yamllint==1.33.0 and fails with yamllint==1.34.0 (because of `yamllint.rules.truthy.TRUTHY`, removed): |
| from yamllint.rules.truthy import TRUTHY",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `yamllint.rules.truthy.TRUTHY`, not from the placeholder arguments." |
| C096,breaking_change_claim,azure-search-documents,11.6.0,12.0.0,`azure.search.documents.indexes.models.EntityRecognitionSkillVersion` can be used in 11.6.0 but no longer exists in 12.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-search-documents==11.6.0'` and `pip install 'azure-search-documents==12.0.0'`; in each run `python check_item.py azure.search.documents.indexes.models.EntityRecognitionSkillVersion`. Release notes, changelogs and documentation are also valid evidence." |
| C049,breaking_change_claim,azure-mgmt-web,10.1.0,11.0.0,`azure.mgmt.web.models.ScaleRule` can be used in 10.1.0 but no longer exists in 11.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-web==10.1.0'` and `pip install 'azure-mgmt-web==11.0.0'`; in each run `python check_item.py azure.mgmt.web.models.ScaleRule`. Release notes, changelogs and documentation are also valid evidence." |
| C157,breaking_change_claim,tensorflow,2.2.3,2.3.2,`tensorflow.python.serialize_tensor_eager_fallback` can be used in 2.2.3 but no longer exists in 2.3.2. (detail: still available as tensorflow.python.ops.parsing_ops.serialize_tensor_eager_fallback),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'tensorflow==2.2.3'` and `pip install 'tensorflow==2.3.2'`; in each run `python check_item.py tensorflow.python.serialize_tensor_eager_fallback`. Release notes, changelogs and documentation are also valid evidence." |
| C149,breaking_change_claim,diffusers,0.28.2,0.29.0,`diffusers.utils.dynamic_modules_utils.COMMUNITY_PIPELINES_URL` can be used in 0.28.2 but no longer exists in 0.29.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'diffusers==0.28.2'` and `pip install 'diffusers==0.29.0'`; in each run `python check_item.py diffusers.utils.dynamic_modules_utils.COMMUNITY_PIPELINES_URL`. Release notes, changelogs and documentation are also valid evidence." |
| C027,breaking_change_claim,polyfactory,2.2.0,2.3.0,`polyfactory.field_meta.FieldMeta` gained a new required parameter `random` in 2.3.0; calls valid in 2.2.0 fail. (detail: KO),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'polyfactory==2.2.0'` and `pip install 'polyfactory==2.3.0'`; in each run `python check_item.py polyfactory.field_meta.FieldMeta --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C047,breaking_change_claim,types-boto3-s3,1.36.9,1.36.15,`types_boto3_s3.type_defs.GetBucketOwnershipControlsRequestRequestTypeDef` can be used in 1.36.9 but no longer exists in 1.36.15.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'types-boto3-s3==1.36.9'` and `pip install 'types-boto3-s3==1.36.15'`; in each run `python check_item.py types_boto3_s3.type_defs.GetBucketOwnershipControlsRequestRequestTypeDef`. Release notes, changelogs and documentation are also valid evidence." |
| C144,breaking_change_claim,keras,2.10.0,2.11.0,`keras.utils.generic_utils.get_custom_objects` can be used in 2.10.0 but no longer exists in 2.11.0. (detail: still available as keras.utils.get_custom_objects),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'keras==2.10.0'` and `pip install 'keras==2.11.0'`; in each run `python check_item.py keras.utils.generic_utils.get_custom_objects`. Release notes, changelogs and documentation are also valid evidence." |
| C079,breaking_change_claim,bokeh,3.1.0,3.1.1,The parameter `stats_log_frequency_milliseconds` of `bokeh.server.tornado.BokehTornado` can be passed positionally in 3.1.0 but only by keyword in 3.1.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'bokeh==3.1.0'` and `pip install 'bokeh==3.1.1'`; in each run `python check_item.py bokeh.server.tornado.BokehTornado --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C147,breaking_change_claim,pulp,3.0.2,3.1.1,`pulp.Parser` can be used in 3.0.2 but no longer exists in 3.1.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pulp==3.0.2'` and `pip install 'pulp==3.1.1'`; in each run `python check_item.py pulp.Parser`. Release notes, changelogs and documentation are also valid evidence." |
| C031,breaking_change_claim,dspy,2.5.3,2.5.4,`dsp.DummyLM` can be used in 2.5.3 but no longer exists in 2.5.4. (detail: still available as dspy.utils.DummyLM),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'dspy==2.5.3'` and `pip install 'dspy==2.5.4'`; in each run `python check_item.py dsp.DummyLM`. Release notes, changelogs and documentation are also valid evidence." |
| C139,breaking_change_claim,python-telegram-bot,13.15,20.0,The parameter `api_kwargs` of `telegram.CallbackQuery.delete_message` can be passed positionally in 13.15 but only by keyword in 20.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'python-telegram-bot==13.15'` and `pip install 'python-telegram-bot==20.0'`; in each run `python check_item.py telegram.CallbackQuery.delete_message --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C037,breaking_change_claim,dynaconf,3.2.13,3.3.0,`dynaconf.loaders.DynaBox` can be used in 3.2.13 but no longer exists in 3.3.0. (detail: still available as dynaconf.utils.boxing.DynaBox),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'dynaconf==3.2.13'` and `pip install 'dynaconf==3.3.0'`; in each run `python check_item.py dynaconf.loaders.DynaBox`. Release notes, changelogs and documentation are also valid evidence." |
| P069,benchmark_pair,docstring-parser,0.16,0.17.0,"This snippet works with docstring-parser==0.16 and fails with docstring-parser==0.17.0 (because of `docstring_parser.attrdoc.ast_constant_attr`, removed): |
| from docstring_parser.attrdoc import ast_constant_attr",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `docstring_parser.attrdoc.ast_constant_attr`, not from the placeholder arguments." |
| C075,breaking_change_claim,azure-functions,1.23.0,1.24.0,The parameter `model` of `azure.functions.decorators.openai.EmbeddingsInput` was renamed between 1.23.0 and 1.24.0; the old name fails in 1.24.0. (detail: model -> ai_connection_name),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-functions==1.23.0'` and `pip install 'azure-functions==1.24.0'`; in each run `python check_item.py azure.functions.decorators.openai.EmbeddingsInput --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C035,breaking_change_claim,azure-mgmt-network,27.0.0,28.0.0,`azure.mgmt.network.models.NetworkRuleCondition` can be used in 27.0.0 but no longer exists in 28.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-network==27.0.0'` and `pip install 'azure-mgmt-network==28.0.0'`; in each run `python check_item.py azure.mgmt.network.models.NetworkRuleCondition`. Release notes, changelogs and documentation are also valid evidence." |
| C143,breaking_change_claim,azure-mgmt-recoveryservices,3.1.0,4.0.0,`azure.mgmt.recoveryservices.models.VaultList` can be used in 3.1.0 but no longer exists in 4.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-recoveryservices==3.1.0'` and `pip install 'azure-mgmt-recoveryservices==4.0.0'`; in each run `python check_item.py azure.mgmt.recoveryservices.models.VaultList`. Release notes, changelogs and documentation are also valid evidence." |
| C012,breaking_change_claim,azure-mgmt-keyvault,12.1.0,12.1.1,`generated_samples.managed_hsm_create_key` can be used in 12.1.0 but no longer exists in 12.1.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-keyvault==12.1.0'` and `pip install 'azure-mgmt-keyvault==12.1.1'`; in each run `python check_item.py generated_samples.managed_hsm_create_key`. Release notes, changelogs and documentation are also valid evidence." |
| C057,breaking_change_claim,faiss-cpu,1.8.0.post1,1.9.0,`faiss.knn_extra_metrics` gained a new required parameter `indexes` in 1.9.0; calls valid in 1.8.0.post1 fail. (detail: PK),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'faiss-cpu==1.8.0.post1'` and `pip install 'faiss-cpu==1.9.0'`; in each run `python check_item.py faiss.knn_extra_metrics --signature`. Release notes, changelogs and documentation are also valid evidence." |
| P364,benchmark_pair,traitlets,5.8.1,5.9.0,"This snippet works with traitlets==5.8.1 and fails with traitlets==5.9.0 (because of `traitlets.config.loader.KeyValueConfigLoader.argcomplete`, removed): |
| from traitlets.config.loader import KeyValueConfigLoader |
| KeyValueConfigLoader.argcomplete",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `traitlets.config.loader.KeyValueConfigLoader.argcomplete`, not from the placeholder arguments." |
| P066,benchmark_pair,dnspython,2.2.1,2.3.0,"This snippet works with dnspython==2.2.1 and fails with dnspython==2.3.0 (because of `dns.rdtypes.txtbase.TXT`, removed): |
| from dns.rdtypes.txtbase import TXT",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `dns.rdtypes.txtbase.TXT`, not from the placeholder arguments." |
| P018,benchmark_pair,cachetools,5.5.2,6.0.0,"This snippet works with cachetools==5.5.2 and fails with cachetools==6.0.0 (because of `cachetools.MRUCache`, removed): |
| from cachetools import MRUCache",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `cachetools.MRUCache`, not from the placeholder arguments." |
| C148,breaking_change_claim,optree,0.13.1,0.14.0,The parameter `func` of `optree.tree_reduce` can be passed by keyword in 0.13.1 but only positionally in 0.14.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'optree==0.13.1'` and `pip install 'optree==0.14.0'`; in each run `python check_item.py optree.tree_reduce --signature`. Release notes, changelogs and documentation are also valid evidence." |
| P237,benchmark_pair,partd,1.2.0,1.3.0,"This snippet works with partd==1.2.0 and fails with partd==1.3.0 (because of `partd.utils.do_nothing`, removed): |
| from partd.utils import do_nothing",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `partd.utils.do_nothing`, not from the placeholder arguments." |
| P279,benchmark_pair,pypdf2,1.27.5,1.27.6,"This snippet works with pypdf2==1.27.5 and fails with pypdf2==1.27.6 (because of `PyPDF2.utils.PdfReadWarning`, removed): |
| from PyPDF2.utils import PdfReadWarning",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `PyPDF2.utils.PdfReadWarning`, not from the placeholder arguments." |
| P094,benchmark_pair,ftfy,6.2.0,6.2.1,"This snippet works with ftfy==6.2.0 and fails with ftfy==6.2.1 (because of `ftfy.bad_codecs.sloppy.PY26`, removed): |
| from ftfy.bad_codecs.sloppy import PY26",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `ftfy.bad_codecs.sloppy.PY26`, not from the placeholder arguments." |
| P244,benchmark_pair,pdfminer-six,20251230,20260107,"This snippet works with pdfminer-six==20251230 and fails with pdfminer-six==20260107 (because of `pdfminer.cmapdb.CMapParser.poll`, removed): |
| from pdfminer.cmapdb import CMapParser |
| CMapParser.poll",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `pdfminer.cmapdb.CMapParser.poll`, not from the placeholder arguments." |
| C058,breaking_change_claim,cerberus,1.3.3,1.3.5,`cerberus.DistributionNotFound` can be used in 1.3.3 but no longer exists in 1.3.5.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'cerberus==1.3.3'` and `pip install 'cerberus==1.3.5'`; in each run `python check_item.py cerberus.DistributionNotFound`. Release notes, changelogs and documentation are also valid evidence." |
| C032,breaking_change_claim,azure-mgmt-keyvault,12.1.1,13.0.0,`azure.mgmt.keyvault.models.DeletedVaultListResult` can be used in 12.1.1 but no longer exists in 13.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-keyvault==12.1.1'` and `pip install 'azure-mgmt-keyvault==13.0.0'`; in each run `python check_item.py azure.mgmt.keyvault.models.DeletedVaultListResult`. Release notes, changelogs and documentation are also valid evidence." |
| C145,breaking_change_claim,google-ai-generativelanguage,0.6.18,0.7.0,`google.ai.generativelanguage_v1beta.types.file.VideoMetadata` can be used in 0.6.18 but no longer exists in 0.7.0. (detail: still available as google.ai.generativelanguage.VideoMetadata),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'google-ai-generativelanguage==0.6.18'` and `pip install 'google-ai-generativelanguage==0.7.0'`; in each run `python check_item.py google.ai.generativelanguage_v1beta.types.file.VideoMetadata`. Release notes, changelogs and documentation are also valid evidence." |
| C016,breaking_change_claim,azure-mgmt-redis,14.2.0,14.3.0,`azure.mgmt.redis.models.ErrorDetailAutoGenerated` can be used in 14.2.0 but no longer exists in 14.3.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-redis==14.2.0'` and `pip install 'azure-mgmt-redis==14.3.0'`; in each run `python check_item.py azure.mgmt.redis.models.ErrorDetailAutoGenerated`. Release notes, changelogs and documentation are also valid evidence." |
| C109,breaking_change_claim,sqlfluff,1.3.0,1.3.1,`sqlfluff.dialects.dialect_redshift.CreateDatashareStatementSegment` accepts the parameter `name` in 1.3.0 but not in 1.3.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'sqlfluff==1.3.0'` and `pip install 'sqlfluff==1.3.1'`; in each run `python check_item.py sqlfluff.dialects.dialect_redshift.CreateDatashareStatementSegment --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C142,breaking_change_claim,torchmetrics,0.2.0,0.3.0,"The positional parameters of `torchmetrics.functional.f1` were reordered between 0.2.0 and 0.3.0. (detail: ['preds', 'target', 'num_classes', 'threshold', 'average'] -> ['preds', 'target', 'average', 'num_classes', 'threshold'])",Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'torchmetrics==0.2.0'` and `pip install 'torchmetrics==0.3.0'`; in each run `python check_item.py torchmetrics.functional.f1 --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C024,breaking_change_claim,yt-dlp,2023.7.6,2023.9.24,`yt_dlp.compat.passthrough_module` can be used in 2023.7.6 but no longer exists in 2023.9.24. (detail: still available as yt_dlp.compat.compat_utils.passthrough_module),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'yt-dlp==2023.7.6'` and `pip install 'yt-dlp==2023.9.24'`; in each run `python check_item.py yt_dlp.compat.passthrough_module`. Release notes, changelogs and documentation are also valid evidence." |
| C062,breaking_change_claim,google-cloud-dlp,3.8.1,3.9.0,`google.cloud.dlp_v2.types.dlp.SensitivityScore` can be used in 3.8.1 but no longer exists in 3.9.0. (detail: still available as google.cloud.dlp.SensitivityScore),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'google-cloud-dlp==3.8.1'` and `pip install 'google-cloud-dlp==3.9.0'`; in each run `python check_item.py google.cloud.dlp_v2.types.dlp.SensitivityScore`. Release notes, changelogs and documentation are also valid evidence." |
| C018,breaking_change_claim,rich-argparse,1.7.0,1.7.1,The parameter `console` of `rich_argparse.MetavarTypeRichHelpFormatter` can be passed positionally in 1.7.0 but only by keyword in 1.7.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'rich-argparse==1.7.0'` and `pip install 'rich-argparse==1.7.1'`; in each run `python check_item.py rich_argparse.MetavarTypeRichHelpFormatter --signature`. Release notes, changelogs and documentation are also valid evidence." |
| C108,breaking_change_claim,azure-mgmt-managementgroups,1.0.0,1.1.0,`azure.mgmt.managementgroups.operations.ManagementGroupsAPIOperationsMixin` can be used in 1.0.0 but no longer exists in 1.1.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-managementgroups==1.0.0'` and `pip install 'azure-mgmt-managementgroups==1.1.0'`; in each run `python check_item.py azure.mgmt.managementgroups.operations.ManagementGroupsAPIOperationsMixin`. Release notes, changelogs and documentation are also valid evidence." |
| C112,breaking_change_claim,google-cloud-dataproc,3.3.2,4.0.0,`google.cloud.dataproc_v1.types.clusters.GkeClusterConfig` can be used in 3.3.2 but no longer exists in 4.0.0. (detail: still available as google.cloud.dataproc.GkeClusterConfig),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'google-cloud-dataproc==3.3.2'` and `pip install 'google-cloud-dataproc==4.0.0'`; in each run `python check_item.py google.cloud.dataproc_v1.types.clusters.GkeClusterConfig`. Release notes, changelogs and documentation are also valid evidence." |
| C023,breaking_change_claim,mitmproxy,9.0.1,10.0.0,`mitmproxy.addons.next_layer.NextLayer.ignore_connection` can be used in 9.0.1 but no longer exists in 10.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'mitmproxy==9.0.1'` and `pip install 'mitmproxy==10.0.0'`; in each run `python check_item.py mitmproxy.addons.next_layer.NextLayer.ignore_connection`. Release notes, changelogs and documentation are also valid evidence." |
| C010,breaking_change_claim,netaddr,0.9.0,0.10.0,`netaddr.core.a` can be used in 0.9.0 but no longer exists in 0.10.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'netaddr==0.9.0'` and `pip install 'netaddr==0.10.0'`; in each run `python check_item.py netaddr.core.a`. Release notes, changelogs and documentation are also valid evidence." |
| C055,breaking_change_claim,aws-cdk-lib,2.223.0,2.224.0,`aws_cdk.aws_cloudfront.VpcOriginReference` can be used in 2.223.0 but no longer exists in 2.224.0. (detail: still available as aws_cdk.interfaces.aws_cloudfront.VpcOriginReference),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'aws-cdk-lib==2.223.0'` and `pip install 'aws-cdk-lib==2.224.0'`; in each run `python check_item.py aws_cdk.aws_cloudfront.VpcOriginReference`. Release notes, changelogs and documentation are also valid evidence." |
| C130,breaking_change_claim,python-gitlab,3.15.0,4.0.0,`gitlab.NOTIFICATION_LEVEL_WATCH` can be used in 3.15.0 but no longer exists in 4.0.0. (detail: still available as gitlab.const.NOTIFICATION_LEVEL_WATCH),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'python-gitlab==3.15.0'` and `pip install 'python-gitlab==4.0.0'`; in each run `python check_item.py gitlab.NOTIFICATION_LEVEL_WATCH`. Release notes, changelogs and documentation are also valid evidence." |
| C015,breaking_change_claim,azure-mgmt-loganalytics,12.0.0,13.1.0,`azure.mgmt.loganalytics.models.CapacityReservationLevel` can be used in 12.0.0 but no longer exists in 13.1.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-loganalytics==12.0.0'` and `pip install 'azure-mgmt-loganalytics==13.1.0'`; in each run `python check_item.py azure.mgmt.loganalytics.models.CapacityReservationLevel`. Release notes, changelogs and documentation are also valid evidence." |
| C150,breaking_change_claim,elementpath,3.0.1,3.0.2,`elementpath.xpath31.xpath31_parser.infixr` can be used in 3.0.1 but no longer exists in 3.0.2.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'elementpath==3.0.1'` and `pip install 'elementpath==3.0.2'`; in each run `python check_item.py elementpath.xpath31.xpath31_parser.infixr`. Release notes, changelogs and documentation are also valid evidence." |
| C094,breaking_change_claim,pyelftools,0.32,0.33,`elftools.dwarf.callframe.DW_LANG_Python` can be used in 0.32 but no longer exists in 0.33. (detail: still available as elftools.dwarf.constants.DW_LANG_Python),Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pyelftools==0.32'` and `pip install 'pyelftools==0.33'`; in each run `python check_item.py elftools.dwarf.callframe.DW_LANG_Python`. Release notes, changelogs and documentation are also valid evidence." |
| C025,breaking_change_claim,azure-mgmt-servicebus,8.2.1,9.0.0,`azure.mgmt.servicebus.v2018_01_01_preview` can be used in 8.2.1 but no longer exists in 9.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-servicebus==8.2.1'` and `pip install 'azure-mgmt-servicebus==9.0.0'`; in each run `python check_item.py azure.mgmt.servicebus.v2018_01_01_preview`. Release notes, changelogs and documentation are also valid evidence." |
| C138,breaking_change_claim,mistral-vibe,2.11.1,2.12.1,`vibe.core.teleport.nuage.WorkflowExecuteResponse` can be used in 2.11.1 but no longer exists in 2.12.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'mistral-vibe==2.11.1'` and `pip install 'mistral-vibe==2.12.1'`; in each run `python check_item.py vibe.core.teleport.nuage.WorkflowExecuteResponse`. Release notes, changelogs and documentation are also valid evidence." |
| C019,breaking_change_claim,azure-mgmt-containerinstance,9.2.0,10.0.0,`azure.mgmt.containerinstance.models.Components10Wh5UdSchemasContainergroupidentityPropertiesUserassignedidentitiesAdditionalproperties` can be used in 9.2.0 but no longer exists in 10.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-containerinstance==9.2.0'` and `pip install 'azure-mgmt-containerinstance==10.0.0'`; in each run `python check_item.py azure.mgmt.containerinstance.models.Components10Wh5UdSchemasContainergroupidentityPropertiesUserassignedidentitiesAdditionalproperties`. Release notes, changelogs and documentation are also valid evidence." |
| C013,breaking_change_claim,azure-mgmt-rdbms,10.1.0,10.1.1,`azure.mgmt.rdbms.mysql.operations.MySQLManagementClientOperationsMixin` can be used in 10.1.0 but no longer exists in 10.1.1.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-rdbms==10.1.0'` and `pip install 'azure-mgmt-rdbms==10.1.1'`; in each run `python check_item.py azure.mgmt.rdbms.mysql.operations.MySQLManagementClientOperationsMixin`. Release notes, changelogs and documentation are also valid evidence." |
| P046,benchmark_pair,databricks-labs-blueprint,0.0.5,0.0.6,"This snippet works with databricks-labs-blueprint==0.0.5 and fails with databricks-labs-blueprint==0.0.6 (because of `databricks.labs.blueprint.entrypoint.find_project_root`, param_removed `current`): |
| from databricks.labs.blueprint.entrypoint import find_project_root |
| find_project_root(current=...)",Is the label pair correct (valid in the old release AND invalid in the new one)?,"Run the snippet's imports and calls (with placeholder arguments where needed) in fresh environments with each release; a failure must come from `databricks.labs.blueprint.entrypoint.find_project_root`, not from the placeholder arguments." |
| C102,breaking_change_claim,azure-mgmt-resource,24.0.0,25.0.0,`azure.mgmt.resource.resources.models.DebugSetting` can be used in 24.0.0 but no longer exists in 25.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-resource==24.0.0'` and `pip install 'azure-mgmt-resource==25.0.0'`; in each run `python check_item.py azure.mgmt.resource.resources.models.DebugSetting`. Release notes, changelogs and documentation are also valid evidence." |
| C039,breaking_change_claim,azure-mgmt-containerregistry,14.0.0,15.0.0,`azure.mgmt.containerregistry.models.PrivateEndpointConnectionListResult` can be used in 14.0.0 but no longer exists in 15.0.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'azure-mgmt-containerregistry==14.0.0'` and `pip install 'azure-mgmt-containerregistry==15.0.0'`; in each run `python check_item.py azure.mgmt.containerregistry.models.PrivateEndpointConnectionListResult`. Release notes, changelogs and documentation are also valid evidence." |
| C083,breaking_change_claim,pandera,0.29.0,0.30.0,`pandera.PANDAS_2_0_0_PLUS` can be used in 0.29.0 but no longer exists in 0.30.0.,Is the claim correct (code written for the old release that relies on this fails on the new one)?,"In two fresh virtual environments, `pip install 'pandera==0.29.0'` and `pip install 'pandera==0.30.0'`; in each run `python check_item.py pandera.PANDAS_2_0_0_PLUS`. Release notes, changelogs and documentation are also valid evidence." |
|
|
