Trevor Mack

In my scenario I wasn't purposefully making an infinite nesting behavior... so I've now split the swagger data types to prevent an indefinite nesting and instead just a 2 layer...

Similar @adamreisnz there are a few issues that have mentioned this. I've just now started to get annoyed by it enough to try to update and found the same as...

The value I'm looking for is held within `GitHubPullRequestCause.label` just to expose that so I can setup a project's .ci.yml to do specific tasks when we receive a pull request...

Workaround is to change `mysql2` to `mysql` and reissue the `ghost start` command for the impacted site.

I definitely didn't change it myself... so must have been done in migrating from an older version of ghost via the ghost-cli. The issue for me is that this change...

After the upgrade there were other modifications made to the config.production.yamlThere was another change that happened where I lost my earlier configured `mail` configuration and had to reset that up...

`ghost upgrade` 🙂

I didn't even know about this `mysql2` until this error happened which got me to dig down the rabbit hole to see where this would go.

Along my upgrade path I did have to wonder into the weeds to fix the collation issue that was due to the MySql version upgrade (not the client) -> https://forum.ghost.org/t/unable-to-upgrade-ghost-from-v4-2-0-to-v4-3-0-cascade-unknown-code-please-report/22086/56...

Maybe one could go ahead and edit the sources.list directly and mark the specific ppa repository here as trusted like the following, but even doing that and doing a limited...