Repository navigation
Release 1.1.0 - #163
Merged
Merged
Release 1.1.0#163
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dates the changelog section for 1.1.0. One change in it, merged in #161 (closes #155): a shrink candidate is accepted only when it fails the same way the original run did — the same exception class and the same place in the property's own file.
Why a minor rather than a patch: what a descent minimises to may differ from 1.0.0 on a body that can fail in more than one place, which the compatibility policy §2 places outside SemVer but which is still worth a version number people can pin against. No
@apitype, method or parameter changed,FilesystemCorpus::FORMAT_VERSIONandSEQUENCE_EPOCHare untouched, and a corpus recorded under 1.0.0 replays unchanged.Nothing to do in the adapters: they require
rasuvaeff/property-testing-core: ^1.0, which resolves 1.1.0 — their suites were run against this engine before #161 merged (testo 224, phpunit 139, names 72, all green).The tag goes on the merged commit once this PR's CI is green.