Skip to content

[bot] Merge 26.3 to 26.7 (Conflicts) - #1862

Open
github-actions[bot] wants to merge 4 commits into
release26.7-SNAPSHOTfrom
26.7_fb_bot_merge_26.3
Open

[bot] Merge 26.3 to 26.7 (Conflicts)#1862
github-actions[bot] wants to merge 4 commits into
release26.7-SNAPSHOTfrom
26.7_fb_bot_merge_26.3

Conversation

@github-actions

Copy link
Copy Markdown

Automatic merge failed! Please merge 26.3 into 26.7_fb_bot_merge_26.3 and resolve conflicts manually.

git fetch
git checkout 26.7_fb_bot_merge_26.3
git reset --hard origin/release26.7-SNAPSHOT
git merge 22194f3ba2c608bb1679baea8106921e98283b6c -m "Merge 26.3 to 26.7"

Resolve all conflicts (using IntelliJ or git mergetool)

git commit
git push --force

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.7_fb_bot_merge_26.3

labkey-adam and others added 4 commits August 18, 2026 06:52
#1845)

Modified program to allow new formating for demogrphics cagemates
listings.
## Rationale
These modules are now designated as "managed" (to enable script
consolidation, migration, and other build-in script-management tools).
The `AdminController$SchemaVersionTestCase` expects all managed modules
to be at 26.000 or beyond. This clears the test failure.

## Related Pull Requests
- #1805
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.

3 participants