Skip to content

[pull] main from TryGhost:main - #1501

Merged
pull[bot] merged 13 commits into
code:mainfrom
TryGhost:main
Sep 17, 2026
Merged

pull[bot] merged 13 commits into
code:mainfrom
TryGhost:main

Conversation

@pull

@pull pull Bot commented Sep 17, 2026 •

Copy link
Copy Markdown

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 : )

EvanHahn and others added 13 commits September 17, 2026 11:48
towards https://linear.app/ghost/issue/NY-1621

This change should have no user impact.

This renders automations' descriptions from the server, if applicable.
They're not sent today, but they will be in a future change!

In addition to automated tests, I also manually verified this by hacking
the backend API endpoint to send a description:

![Screenshot of database-backed description](https://github.com/user-attachments/assets/cc1a1c33-06c4-4f68-b1b3-d78ebb38352d)
…t are built

Portal's type check reads @tryghost/metafield-types from that package's build output, but nothing told Nx to build it first. CI only passed while another project in the same run happened to build it, so a change touching Portal alone failed to find the module. Portal's lint now declares the build it needs, the same way Admin's does.
no ref

Each row of an address was a component declared inside the field, so every render made a new component type and React replaced the row's inputs. Typing a key re-renders the field, so the input a member was typing in was torn down after the first character and the rest of what they typed went nowhere. Declaring the row once, outside the field, keeps its inputs mounted across renders. The new browser test types an address line a key at a time and checks the input keeps focus and the whole value.
towards https://linear.app/ghost/issue/NY-1622

Should have no user impact.

I think this is a useful change on its own, but will also make an
upcoming change easier.
towards https://linear.app/ghost/issue/NY-1622

There was no reason for this to return a promise.

Should have no user impact.

I think this is a useful change on its own, but will also make an
upcoming change easier.
no ref

Replaces `_.isArray` with `Array.isArray`.

`_.isArray` is [just an alias for `Array.isArray`][0], so this should
have no effect.

[0]: https://github.com/lodash/lodash/blob/cb0b9b9212521c08e3eafe7c8cb0af1b42b6649e/lodash.js#L11385
no ref

Renovate has not created or merged a dependency PR in weeks. Two
independent faults combined into a deadlock.

`allowedPostUpgradeCommands` was renamed to `allowedCommands` in
Renovate 41, so `RENOVATE_ALLOWED_POST_UPGRADE_COMMANDS` has been
silently ignored since the runner moved to 44. Renovate refused both
changeset postUpgradeTask commands, set `renovate/artifacts` to failure
on every npm branch, and will not automerge a PR carrying an artifact
error.

The open-PR cap counted every PR without a `needs:review` label, but
that label marks only one of the config's automerge exclusions. Docker
digest, pin, and monorepo PRs that Renovate can never merge itself
counted against the cap of 6, pinning the count at 7 and holding the
runner in maintenance-only mode indefinitely. Counting Renovate's own
per-PR automerge marker instead drops the live count to 3 and reopens
PR creation. A body missing the marker still counts, so an unparseable
PR tightens the cap rather than loosening it.
@pull pull Bot locked and limited conversation to collaborators Sep 17, 2026
@pull pull Bot added the ⤵️ pull label Sep 17, 2026
@pull
pull Bot merged commit 821033b into code:main Sep 17, 2026
2 checks passed
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.

4 participants