Skip to content

chore: release 0.26.0 #1034

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
TimothyJones merged 1 commit into from
Jul 11, 2025
Merged

chore: release 0.26.0 #1034

TimothyJones merged 1 commit into from
Jul 11, 2025

Conversation

@TimothyJones
Copy link
Member

@TimothyJones TimothyJones commented Jun 23, 2025 •
edited
Loading

🤖 I have created a release beep boop

@contract-case/case-connector: 0.26.0

0.26.0 (2025-07-11)

Features

  • java-dsl: Now supports the prepareVerificationTests and runPreparedTest lifecycle for better integration with JUnit (1408d46)
  • Now definer.endRecord() returns a ContractWriteSuccess object, which contains details of the written contract(s) (7299895)

Bug Fixes

  • connector: Correct types read when moduleresolution is node (ff29e62)
  • core: availableContractDescriptions now respects the configuration and only returns the filtered set of contracts. This was the intended (and documented) behaviour before. If you need to see the ignored contracts, they're visible in a call to this method with a logLevel of DEBUG or lower. (9c4e5a8)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @contract-case/case-connector-proto bumped from 0.25.2 to 0.26.0
      • @contract-case/case-core bumped from 0.25.2 to 0.26.0
      • @contract-case/case-entities-internal bumped from 0.25.2 to 0.26.0
    • devDependencies
      • @contract-case/case-maintainer-config bumped from 0.25.2 to 0.26.0
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/case-connector-proto: 0.26.0

0.26.0 (2025-07-11)

Features

  • java-dsl: Now supports the prepareVerificationTests and runPreparedTest lifecycle for better integration with JUnit (1408d46)

Dependencies

  • The following workspace dependencies were updated
    • devDependencies
      • @contract-case/case-maintainer-config bumped from 0.25.2 to 0.26.0
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/case-core: 0.26.0

0.26.0 (2025-07-11)

⚠ BREAKING CHANGES

  • core: Removed the assumption that every interaction response can be described by "returns". This is a breaking change, because it needs contracts to be re-written, and http contracts with automatically named triggers will have to change triggers from `"a (200) ..."` to `"returns a (200) ..."`. If you need to stay compatible with contracts from before this version, you will need to provide both names in your trigger definitions

Features

  • core: Now contract verification is guaranteed to run contracts in order, instead of interleaving interactions (0648101)
  • core: Removed the assumption that every interaction response can be described by "returns". This is a breaking change, because it needs contracts to be re-written, and http contracts with automatically named triggers will have to change triggers from `"a (200) ..."` to `"returns a (200) ..."`. If you need to stay compatible with contracts from before this version, you will need to provide both names in your trigger definitions (7f06209)
  • java-dsl: Now supports the prepareVerificationTests and runPreparedTest lifecycle for better integration with JUnit (1408d46)
  • Now definer.endRecord() returns a ContractWriteSuccess object, which contains details of the written contract(s) (7299895)
  • plugin-base: Added ability for matching errors to have context about what the data is, allowing more specific error messages (150c0d6)

Bug Fixes

  • core: availableContractDescriptions now respects the configuration and only returns the filtered set of contracts. This was the intended (and documented) behaviour before. If you need to see the ignored contracts, they're visible in a call to this method with a logLevel of DEBUG or lower. (9c4e5a8)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @contract-case/case-core-plugin-function bumped from 0.25.2 to 0.26.0
      • @contract-case/case-core-plugin-http bumped from 0.25.2 to 0.26.0
      • @contract-case/case-core-plugin-http-dsl bumped from 0.25.2 to 0.26.0
      • @contract-case/case-entities-internal bumped from 0.25.2 to 0.26.0
      • @contract-case/case-plugin-base bumped from 0.25.2 to 0.26.0
      • @contract-case/case-plugin-dsl-types bumped from 0.25.2 to 0.26.0
    • devDependencies
      • @contract-case/case-definition-dsl bumped from 0.25.2 to 0.26.0
      • @contract-case/case-maintainer-config bumped from 0.25.2 to 0.26.0
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/case-core-plugin-function: 0.26.0

0.26.0 (2025-07-11)

⚠ BREAKING CHANGES

  • core: Removed the assumption that every interaction response can be described by "returns". This is a breaking change, because it needs contracts to be re-written, and http contracts with automatically named triggers will have to change triggers from `"a (200) ..."` to `"returns a (200) ..."`. If you need to stay compatible with contracts from before this version, you will need to provide both names in your trigger definitions

Features

  • core: Removed the assumption that every interaction response can be described by "returns". This is a breaking change, because it needs contracts to be re-written, and http contracts with automatically named triggers will have to change triggers from `"a (200) ..."` to `"returns a (200) ..."`. If you need to stay compatible with contracts from before this version, you will need to provide both names in your trigger definitions (7f06209)

Bug Fixes

  • function-plugin: Add debug logging of return value when caller is mocked (cac45b5)
  • function-plugin: No longer repeats returnValue twice in error location messages (4a5d4dd)
  • function-plugin: Substantially improved error messages when functions throw instead of returning, or receive the wrong number of arguments (d25d819)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @contract-case/case-core-plugin-function-dsl bumped from 0.25.2 to 0.26.0
      • @contract-case/case-plugin-base bumped from 0.25.2 to 0.26.0
      • @contract-case/case-plugin-dsl-types bumped from 0.25.2 to 0.26.0
    • devDependencies
      • @contract-case/case-maintainer-config bumped from 0.25.2 to 0.26.0
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/case-core-plugin-function-dsl: 0.26.0

0.26.0 (2025-07-11)

Miscellaneous Chores

  • @contract-case/case-core-plugin-function-dsl: Synchronize ContractCase versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @contract-case/case-plugin-dsl-types bumped from 0.25.2 to 0.26.0
    • devDependencies
      • @contract-case/case-maintainer-config bumped from 0.25.2 to 0.26.0
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/case-core-plugin-http: 0.26.0

0.26.0 (2025-07-11)

⚠ BREAKING CHANGES

  • core: Removed the assumption that every interaction response can be described by "returns". This is a breaking change, because it needs contracts to be re-written, and http contracts with automatically named triggers will have to change triggers from `"a (200) ..."` to `"returns a (200) ..."`. If you need to stay compatible with contracts from before this version, you will need to provide both names in your trigger definitions

Features

  • core: Removed the assumption that every interaction response can be described by "returns". This is a breaking change, because it needs contracts to be re-written, and http contracts with automatically named triggers will have to change triggers from `"a (200) ..."` to `"returns a (200) ..."`. If you need to stay compatible with contracts from before this version, you will need to provide both names in your trigger definitions (7f06209)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @contract-case/case-core-plugin-http-dsl bumped from 0.25.2 to 0.26.0
      • @contract-case/case-plugin-dsl-types bumped from 0.25.2 to 0.26.0
      • @contract-case/case-plugin-base bumped from 0.25.2 to 0.26.0
    • devDependencies
      • @contract-case/case-maintainer-config bumped from 0.25.2 to 0.26.0
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/case-core-plugin-http-dsl: 0.26.0

0.26.0 (2025-07-11)

Miscellaneous Chores

  • @contract-case/case-core-plugin-http-dsl: Synchronize ContractCase versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @contract-case/case-plugin-dsl-types bumped from 0.25.2 to 0.26.0
    • devDependencies
      • @contract-case/case-maintainer-config bumped from 0.25.2 to 0.26.0
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/case-definition-dsl: 0.26.0

0.26.0 (2025-07-11)

Miscellaneous Chores

  • @contract-case/case-definition-dsl: Synchronize ContractCase versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @contract-case/case-core-plugin-function-dsl bumped from 0.25.2 to 0.26.0
      • @contract-case/case-core-plugin-http-dsl bumped from 0.25.2 to 0.26.0
      • @contract-case/case-entities-internal bumped from 0.25.2 to 0.26.0
      • @contract-case/case-plugin-dsl-types bumped from 0.25.2 to 0.26.0
    • devDependencies
      • @contract-case/case-core-plugin-http-dsl bumped from 0.25.2 to 0.26.0
      • @contract-case/case-maintainer-config bumped from 0.25.2 to 0.26.0
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/case-entities-internal: 0.26.0

0.26.0 (2025-07-11)

Miscellaneous Chores

  • @contract-case/case-entities-internal: Synchronize ContractCase versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @contract-case/case-core-plugin-http-dsl bumped from 0.25.2 to 0.26.0
      • @contract-case/case-core-plugin-function-dsl bumped from 0.25.2 to 0.26.0
      • @contract-case/case-plugin-dsl-types bumped from 0.25.2 to 0.26.0
    • devDependencies
      • @contract-case/case-maintainer-config bumped from 0.25.2 to 0.26.0
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/case-maintainer-config: 0.26.0

0.26.0 (2025-07-11)

Miscellaneous Chores

  • @contract-case/case-maintainer-config: Synchronize ContractCase versions
@contract-case/case-plugin-base: 0.26.0

0.26.0 (2025-07-11)

Features

  • plugin-base: Added ability for matching errors to have context about what the data is, allowing more specific error messages (150c0d6)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @contract-case/case-plugin-dsl-types bumped from 0.25.2 to 0.26.0
    • devDependencies
      • @contract-case/case-maintainer-config bumped from 0.25.2 to 0.26.0
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/case-plugin-dsl-types: 0.26.0

0.26.0 (2025-07-11)

Miscellaneous Chores

  • @contract-case/case-plugin-dsl-types: Synchronize ContractCase versions

Dependencies

  • The following workspace dependencies were updated
    • devDependencies
      • @contract-case/case-maintainer-config bumped from 0.25.2 to 0.26.0
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/cli: 0.26.0

0.26.0 (2025-07-11)

Miscellaneous Chores

  • @contract-case/cli: Synchronize ContractCase versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @contract-case/case-connector bumped from 0.25.2 to 0.26.0
      • @contract-case/case-core bumped from 0.25.2 to 0.26.0
    • devDependencies
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/contract-case-jest: 0.26.0

0.26.0 (2025-07-11)

⚠ BREAKING CHANGES

  • core: Removed the assumption that every interaction response can be described by "returns". This is a breaking change, because it needs contracts to be re-written, and http contracts with automatically named triggers will have to change triggers from `"a (200) ..."` to `"returns a (200) ..."`. If you need to stay compatible with contracts from before this version, you will need to provide both names in your trigger definitions

Features

  • Add Jest 30 as a possible peer dependency (0f3cc98)
  • core: Removed the assumption that every interaction response can be described by "returns". This is a breaking change, because it needs contracts to be re-written, and http contracts with automatically named triggers will have to change triggers from `"a (200) ..."` to `"returns a (200) ..."`. If you need to stay compatible with contracts from before this version, you will need to provide both names in your trigger definitions (7f06209)
  • Now definer.endRecord() returns a ContractWriteSuccess object, which contains details of the written contract(s) (7299895)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @contract-case/case-connector bumped from 0.25.2 to 0.26.0
      • @contract-case/case-core-plugin-http-dsl bumped from 0.25.2 to 0.26.0
      • @contract-case/case-definition-dsl bumped from 0.25.2 to 0.26.0
      • @contract-case/case-entities-internal bumped from 0.25.2 to 0.26.0
      • @contract-case/case-plugin-base bumped from 0.25.2 to 0.26.0
      • @contract-case/case-plugin-dsl-types bumped from 0.25.2 to 0.26.0
      • @contract-case/cli bumped from 0.25.2 to 0.26.0
    • devDependencies
      • @contract-case/cli bumped from 0.25.2 to 0.26.0
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/documentation-matchers-generator: 0.26.0

0.26.0 (2025-07-11)

Miscellaneous Chores

  • @contract-case/documentation-matchers-generator: Synchronize ContractCase versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @contract-case/case-definition-dsl bumped from 0.25.2 to 0.26.0
    • devDependencies
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0
@contract-case/dsl-java: 0.26.0

0.26.0 (2025-07-11)

⚠ BREAKING CHANGES

  • core: Removed the assumption that every interaction response can be described by "returns". This is a breaking change, because it needs contracts to be re-written, and http contracts with automatically named triggers will have to change triggers from `"a (200) ..."` to `"returns a (200) ..."`. If you need to stay compatible with contracts from before this version, you will need to provide both names in your trigger definitions

Features

  • core: Removed the assumption that every interaction response can be described by "returns". This is a breaking change, because it needs contracts to be re-written, and http contracts with automatically named triggers will have to change triggers from `"a (200) ..."` to `"returns a (200) ..."`. If you need to stay compatible with contracts from before this version, you will need to provide both names in your trigger definitions (7f06209)
  • java-dsl: Now supports the prepareVerificationTests and runPreparedTest lifecycle for better integration with JUnit (1408d46)
  • Now definer.endRecord() returns a ContractWriteSuccess object, which contains details of the written contract(s) (7299895)

Bug Fixes

  • java-dsl: Ensure that user-facing stack traces include the cause if they are chained exceptions (6ba5326)
  • java-dsl: Plugins were not passed to the core by the Verifier (4791891)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @contract-case/case-connector bumped from 0.25.2 to 0.26.0
      • @contract-case/case-definition-dsl bumped from 0.25.2 to 0.26.0
@contract-case/eslint-config-case-maintainer: 0.26.0

0.26.0 (2025-07-11)

Miscellaneous Chores

  • @contract-case/eslint-config-case-maintainer: Synchronize ContractCase versions
documentation: 0.26.0

0.26.0 (2025-07-11)

Miscellaneous Chores

  • documentation: Synchronize ContractCase versions
0.26.0

0.26.0 (2025-07-11)

⚠ BREAKING CHANGES

  • core: Removed the assumption that every interaction response can be described by "returns". This is a breaking change, because it needs contracts to be re-written, and http contracts with automatically named triggers will have to change triggers from `"a (200) ..."` to `"returns a (200) ..."`. If you need to stay compatible with contracts from before this version, you will need to provide both names in your trigger definitions

Features

  • Add Jest 30 as a possible peer dependency (0f3cc98)
  • core: Now contract verification is guaranteed to run contracts in order, instead of interleaving interactions (0648101)
  • core: Removed the assumption that every interaction response can be described by "returns". This is a breaking change, because it needs contracts to be re-written, and http contracts with automatically named triggers will have to change triggers from `"a (200) ..."` to `"returns a (200) ..."`. If you need to stay compatible with contracts from before this version, you will need to provide both names in your trigger definitions (7f06209)
  • java-dsl: Now supports the prepareVerificationTests and runPreparedTest lifecycle for better integration with JUnit (1408d46)
  • Now definer.endRecord() returns a ContractWriteSuccess object, which contains details of the written contract(s) (7299895)
  • plugin-base: Added ability for matching errors to have context about what the data is, allowing more specific error messages (150c0d6)

Bug Fixes

  • connector: Correct types read when moduleresolution is node (ff29e62)
  • core: availableContractDescriptions now respects the configuration and only returns the filtered set of contracts. This was the intended (and documented) behaviour before. If you need to see the ignored contracts, they're visible in a call to this method with a logLevel of DEBUG or lower. (9c4e5a8)
  • function-plugin: Add debug logging of return value when caller is mocked (cac45b5)
  • function-plugin: No longer repeats returnValue twice in error location messages (4a5d4dd)
  • function-plugin: Substantially improved error messages when functions throw instead of returning, or receive the wrong number of arguments (d25d819)
  • java-dsl: Ensure that user-facing stack traces include the cause if they are chained exceptions (6ba5326)
  • java-dsl: Plugins were not passed to the core by the Verifier (4791891)

Dependencies

  • The following workspace dependencies were updated
    • devDependencies
      • @contract-case/eslint-config-case-maintainer bumped from 0.25.2 to 0.26.0

This PR was generated with Release Please. See documentation.

@TimothyJones TimothyJones force-pushed the release-please--branches--main branch 2 times, most recently from 9f95b30 to cb10518 Compare June 30, 2025 09:34
@TimothyJones TimothyJones force-pushed the release-please--branches--main branch 6 times, most recently from d2d6bc9 to 5718c80 Compare July 7, 2025 11:50
@TimothyJones TimothyJones changed the title chore: release 0.25.3 chore: release 0.26.0 Jul 8, 2025
@TimothyJones TimothyJones force-pushed the release-please--branches--main branch 4 times, most recently from 1323200 to 868616a Compare July 10, 2025 14:08
@TimothyJones TimothyJones force-pushed the release-please--branches--main branch from 868616a to 88eb624 Compare July 11, 2025 00:50
@TimothyJones TimothyJones merged commit 4c2909c into main Jul 11, 2025
5 of 14 checks passed
@TimothyJones TimothyJones deleted the release-please--branches--main branch July 11, 2025 01:11
@TimothyJones
Copy link
Member Author

TimothyJones commented Jul 11, 2025

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

autorelease: tagged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@TimothyJones