Upgrade to 7.0.5

[hawkyre]

Fixes https://github.com/doofinder/support/issues/3171

Upgrade library version to 7.0.5

After this, the package needs to be updated in https://packagist.org/packages/doofinder/doofinder

[hawkyre]

I have no idea why it's failing if I haven't changed the lockfile at all

[teoortuno]

I have no idea why it's failing if I haven't changed the lockfile at all

Maybe that's the problem. Look at the logs of CI:

# Lock file errors
- The lock file is not up to date with the latest changes in composer.json, it is recommended that you run `composer update` or `composer update <package name>`.

[JoeZ99]

I have no idea why it's failing if I haven't changed the lockfile at all

have you tried what they suggest in the "Details" of each failed run?

[teoortuno]

Why is this downgrading?

[teoortuno]

This is downgrading too.

[teoortuno]

This is also downgrading.

[teoortuno]

And this.

[teoortuno]

Look at this branch: master...refs/heads/teo/test

All I have done is:

1. Do the changes in CHANGELOG.md
2. Update the version in composer.json file
3. Run composer update doofinder/php-doofinder

That's it. No need to change CI flow. All checks passed.

[teoortuno]

With this, the composer validate is validating the composer.lock that is modified by composer update, not the composer.lock that is in git. So it's not doing the proper validation. There will be failures checking the content hash of the lock file.

There's no need to do a composer update every time in CI. We do a composer install later already.

[hawkyre]

@teoortuno Of course, the old CI does NOT use the PHP versions it says it does. It was broken since it was created. Take a look at it, you'll see nowhere it sets the PHP version other than the CI flow title.

[hawkyre]

Obviously it will work, it's just using the same version for every flow and it's the same version as the one used to generate the lockfile.

[teoortuno]

@teoortuno Of course, the old CI does NOT use the PHP versions it says it does. It was broken since it was created. Take a look at it, you'll see nowhere it sets the PHP version other than the CI flow title.

D'oh! Yeah, good catch.

But I still think that the composer validate must be made before the composer update.

[hawkyre]

So we can just do validate then update?

[hawkyre]

Let me see

[hawkyre]

It's failing now @teoortuno

[hawkyre]

With the same error that made me put composer update before validate actually

[teoortuno]

With the same error that made me put composer update before validate actually

Run composer update doofinder/php-doofinder in your environment. That should update the content-hash in composer.lock file.