Skip to content

Upgrade examine to 3.7.1 #19186

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.

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

Merged
merged 1 commit into from
Apr 29, 2025
Merged

Conversation

dawoe
Copy link
Contributor

@dawoe dawoe commented Apr 29, 2025

Prerequisites

  • I have added steps to test this contribution in the description below

Description

We have a Umbraco 13.8.0 website running on Azure WebApps and configured as recommended in the documentation.

On a regular basis Examine indexes are corrupted. The only option is to manually delete them and restart the application to fix the problem.

See the following issues for more details :
Shazwazza/Examine#402
#16163

Last week we updated to Examine 3.7.1 and we have not seen the issue anymore.

This PR updates Examine for V13. Hopefully this can be taken into the next minor release.

Copy link

Hi there @dawoe, thank you for this contribution! 👍

While we wait for one of the Core Collaborators team to have a look at your work, we wanted to let you know about that we have a checklist for some of the things we will consider during review:

  • It's clear what problem this is solving, there's a connected issue or a description of what the changes do and how to test them
  • The automated tests all pass (see "Checks" tab on this PR)
  • The level of security for this contribution is the same or improved
  • The level of performance for this contribution is the same or improved
  • Avoids creating breaking changes; note that behavioral changes might also be perceived as breaking
  • If this is a new feature, Umbraco HQ provided guidance on the implementation beforehand
  • 💡 The contribution looks original and the contributor is presumably allowed to share it

Don't worry if you got something wrong. We like to think of a pull request as the start of a conversation, we're happy to provide guidance on improving your contribution.

If you realize that you might want to make some changes then you can do that by adding new commits to the branch you created for this work and pushing new commits. They should then automatically show up as updates to this pull request.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

Copy link
Contributor

@AndyButland AndyButland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dawoe - yes, we'll include this in the next releases.

@AndyButland
Copy link
Contributor

Merging, as failing E2E tests are not related.

@AndyButland AndyButland merged commit 8d85259 into umbraco:v13/contrib Apr 29, 2025
16 of 20 checks passed
@iOvergaard iOvergaard added the dependencies Pull requests that update a dependency file label May 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants