Skip to content

[bot] Merge 26.3 to 26.4#7581

Merged
github-actions[bot] merged 15 commits intorelease26.4-SNAPSHOTfrom
26.4_fb_bot_merge_26.3
Apr 14, 2026
Merged

[bot] Merge 26.3 to 26.4#7581
github-actions[bot] merged 15 commits intorelease26.4-SNAPSHOTfrom
26.4_fb_bot_merge_26.3

Conversation

@github-actions
Copy link
Copy Markdown

Generated automatically.
Merging changes from: c11d7dc
Approve all matching PRs simultaneously.
Approval will trigger automatic merge.
Verify all PRs before approving: https://internal.labkey.com/Scrumtime/Backlog/harvest-gitOpenPullRequests.view?branch=26.4_fb_bot_merge_26.3

labkey-matthewb and others added 15 commits April 7, 2026 10:28
#### Rationale
fix getBlankSql()
[issue #1033
](LabKey/internal-issues#1033)

#### Related Pull Requests
- <!-- list of links to related pull requests (replace this comment) -->

#### Changes
- <!-- list of descriptions of changes that are worth noting (replace
this comment) -->


#### Tasks 📍
- [x] Needs Automation
#### Rationale
LabKey/internal-issues#901

Fixes auto-link from samples when subject and timepoint information are
linked through lineage sources. Prior to this change all information
could only be sourced from the same container, now for product folders
the container filter is generated.

Also implement the equivalent to `getContainerFilterForFolder` for the
server that exists in our client code.

#### Related Pull Requests
#7552
LabKey/limsModules#2095
LabKey/labkey-ui-premium#929

---------

Co-authored-by: cnathe <cnathe@labkey.com>
#### Rationale
Restricted issues were previously not getting indexed by the crawler
because the search user did not have access to all of the issues. If the
index were deleted, these issues would never reappear in the index
unless they were resaved by a user with access.

This change ensures that all restricted issues can be indexed by the
crawler. Additionally any restricted issues that appear in the search
summary will not render any comments. Instead, a warning will be
displayed to inform the user that they do not have access to that
restricted issue. As was the behavior prior, clicking on the details
link will generate an unauthorized exception.
#### Rationale
`XmlBeansUtil.DOCUMENT_BUILDER_FACTORY` sets
`disallow-doctype-decl=true` for XXE protection, which causes parsers to
fail on any XML with a `<!DOCTYPE>` declaration. This is a problem for
the Panorama Public code that parses NCBI's `esummary.fcgi` response
that begins with `<!DOCTYPE eSummaryResult PUBLIC ... esummary-v1.dtd>`

#### Related Pull Requests
- LabKey/MacCossLabModules#605
- LabKey/MacCossLabModules#623

#### Changes
- Added `DOCUMENT_BUILDER_FACTORY_ALLOWING_DOCTYPE` to `XmlBeansUtil`,
mirroring the existing `SAX_PARSER_FACTORY_ALLOWING_DOCTYPE`. The
DOCTYPE declaration is permitted, but every other XXE mitigation stays
in place.
- Extracted a private `documentBuilderFactory(boolean allowDocType)`
helper, mirroring the existing `saxParserFactory(boolean)` helper.
#### Rationale
The error is a bit overaggressive. It would be normal to not include
subject/timepoint information in sample imports that have autolink
configured.

Reverting back to ignoring the row.
#### Rationale
MCP tool validateSql() to go along with the metadata tools

#### Related Pull Requests
* LabKey/premiumModules#510

#### Changes
* <!-- list of descriptions of changes that are worth noting (replace
this comment) -->
#### Changes
- Add additional validation to `MothershipTest.testIgnoreExceptionFromDataRegion`
- Prevent memory leak after `ListManager.TestCase`
- `null` out static variables before deleting test container so that container deletion errors can't cause other leaks
@github-actions github-actions bot merged commit 50e369b into release26.4-SNAPSHOT Apr 14, 2026
9 checks passed
@github-actions github-actions bot deleted the 26.4_fb_bot_merge_26.3 branch April 14, 2026 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants