Bump version to 1.1.0 - #6
Open
jvmvik wants to merge 1 commit into
Open
Conversation
New features since 1.0.0, all backwards compatible: connection reuse, default search parameters in the constructor, associative array decoding, API key masking in debug output and Markdown output. A minor bump under semver. Client::VERSION also feeds the `source` query parameter, so requests now report `serpapi-php:1.1.0` and the new release is distinguishable in usage statistics. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Bumps
Client::VERSIONfrom1.0.0to1.1.0, plus the README change log.Why a minor bump
New features since 1.0.0, all backwards compatible:
persistent,close())assoc)__debugInfo(),inspect())markdown(),search_archive($id, 'md'))No removals and no signature breaks, so a minor bump under semver rather than a major one.
Side effect worth knowing
Client::VERSIONalso feeds thesourcequery parameter, so requests will start reportingserpapi-php:1.1.0instead ofserpapi-php:1.0.0. That is the intent — it makes the new release distinguishable in usage statistics — but it does mean this PR changes what goes over the wire, not just a constant.Verified:
Client::SOURCEresolves toserpapi-php:1.1.0, PHPStan level 6 clean, 108 tests passing.For the reviewer
Based on
feature/ruby-parity(#3), notInit, since it is those features this bump is versioning. Merge order: #3, then #5 (Markdown), then this.composer.jsonintentionally carries noversionfield — Packagist derives it from the git tag, and a hardcoded field would be a second source of truth to keep in sync. Tagging1.1.0after merge is what actually publishes the release.Related: the repo has no
CHANGELOG.md; the change log lives as a README section, which is what this PR updates. Splitting it into a real changelog file is worth doing separately.🤖 Generated with Claude Code