Skip to content

Dependencies: Upgrade Examine to 3.8.0 - #23075

Merged
AndyButland merged 1 commit into
umbraco:mainfrom
si25:v13,v16,v17/Upgrade-examine-to-3.8.0
Jun 5, 2026
Merged

Dependencies: Upgrade Examine to 3.8.0#23075
AndyButland merged 1 commit into
umbraco:mainfrom
si25:v13,v16,v17/Upgrade-examine-to-3.8.0

Conversation

@si25

@si25 si25 commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Prerequisites

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

If there's an existing issue for this PR then this fixes

Description

I have an Umbraco 13.14.0 running on Umbraco Cloud which is configured as suggested.

We recently started to see an issue where an Examine index is left locked after Azure performs a platform file storage recycle, which prevents search components from recovering. This results in a 500 error on any page using search until the instance is rebooted.

More details here: Shazwazza/Examine#434

Appreciate v13 is out of support phase, but hopefully this could be merged into a minor

@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown

Hi there @si25, 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 🤖 🙂

@AndyButland AndyButland changed the title Upgrade Examine to 3.8.0 Dependencies: Upgrade Examine to 3.8.0 Jun 5, 2026

@AndyButland AndyButland left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks @si25. Will merge this in and cherry-pick back for 17, which will mean this updates will land in 17.6 and 18.1.

I'll have some discussions internally to see if we want to accelerate that and/or also ship out of support versions with an update.

I believe should you want to use this before Umbraco releases updates, you can make a project reference to this version of Examine directly - i.e. take a dependency yourself on Examine and Examine.Core 3.8 in your own project.

@AndyButland
AndyButland merged commit a3424eb into umbraco:main Jun 5, 2026
31 checks passed
AndyButland pushed a commit that referenced this pull request Jun 5, 2026
Upgrade Examine to 3.8.0

Co-authored-by: Simon Gibbs <sgibbs@qmu.ac.uk>
@si25

si25 commented Jun 5, 2026

Copy link
Copy Markdown
Contributor Author

Thanks Andy, appreciate it. Yes a slight edge case with v13 on Cloud, as the fix seems to be for a regression following Azure making an app service change but doesn't seem to be a mechanism to roll it out without an update to the CMS

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