Skip to content

[pull] main from TryGhost:main#1210

Merged
pull[bot] merged 10 commits into
code:mainfrom
TryGhost:main
Jun 4, 2026
Merged

[pull] main from TryGhost:main#1210
pull[bot] merged 10 commits into
code:mainfrom
TryGhost:main

Conversation

@pull
Copy link
Copy Markdown

@pull pull Bot commented Jun 4, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

kevinansfield and others added 10 commits June 4, 2026 12:33
Admin search performance is under investigation after the dependency
bump in ecab07e. This reverts only the
admin package while that investigation continues.
Introduced a shared notification email primitive. It takes a resolved
recipient list, sanitises the content, renders it inside a styled shell
per recipient, and sends. The shell holds the chrome so notifications
stay short and semantic. The sanitiser strips scripts, inline handlers
and unsafe links so an untrusted upstream source cannot ship a phishing
or injection payload through this path.
/llms-full.txt previously walked the full public post catalogue while
building a single bounded response. On large publications that made
generation latency scale with total post count, even though the response
is already constrained by a 5 MiB output budget.

This bounds the full export to public pages plus the latest 500 public
posts. That keeps /llms-full.txt useful as a consolidated context file
while giving generation a predictable upper bound of five post pages.
The complete public content index remains available in /llms.txt, and a
footer is added when the recent-post cap is reached so consumers know
where to discover older content.

The budget check now tracks generated byte length incrementally instead
of repeatedly measuring the whole growing output for every candidate
entry. Both truncation and recent-post footer sizes are reserved up
front, so the generated response stays within the configured budget no
matter which footer is needed.
ref https://linear.app/ghost/issue/BER-3700/refactor-comment-api-querying

Consolidates the comments service's scattered comment-by-ID fetches into a small set of shared, status-aware lookups. Each filters status in the query and selects the internal columns the follow-up logic relies on, so field-limited API requests still resolve correctly.
no ref

This change should have no user impact.
no ref

This change should have no user impact.
Follow-up to #44af74370c, which made the adapter "missing dependency"
error reachable again. That error said dependencies were missing but not
*which* one.

This parses the module name from the `MODULE_NOT_FOUND` first line and
includes it:

> You are missing a dependency `'superagent'` in your adapter
`core/server/adapters/scheduling/SchedulingPro`

Falls back to the existing wording if no specifier can be parsed. Minor
actionability improvement, no behavior change.

- `adapter-manager.js`: extract and include the unresolved module name
- `adapter-manager.test.js`: assert the name appears in the error
closes https://linear.app/ghost/issue/ONC-1808/

## Summary
- Keeps admin search index refreshes alive across restartable search keystrokes
- Expires cached admin search content when indexed post fields change or posts are deleted
- Adds the direct chalk dependency required by the admin Ember build under pnpm

## Root cause
`searchTask` is restartable, so refresh task instances started from it were cancelled on later keystrokes while the underlying AJAX requests continued. That left the cache stale and allowed another full search-index refresh to start.

The fix starts refreshes with `refreshContentTask.unlinked().perform()` so the refresh task is not linked to the restartable search task that triggered it. That lets the in-flight index refresh complete and update the shared cache, while the provider's `drop` task behavior still prevents duplicate refreshes from starting.
@pull pull Bot locked and limited conversation to collaborators Jun 4, 2026
@pull pull Bot added the ⤵️ pull label Jun 4, 2026
@pull pull Bot merged commit 4f90620 into code:main Jun 4, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants