4f97ee2dab
## What <!-- * Describe what the change is solving. Link all GitHub issues related to this change. --> This pull request updates plan names across most of the Documentation so they're consistent with our current plan names. ## How <!-- * Describe how code changes achieve the solution. --> My original plan was to convert free text to MDX variables so we only had to make future updates to names in one place. While broadly successful, there were numerous edge cases that made rolling this out almost impossible. There were too many ways and places you couldn't use variables due to a variety of limitations in Docusaurus and Airbyte's internal MarkDown processor. Explaining how to properly use them made me realize how prohibitively insufficient this was. In the end, I opted to return to using free text for plan names. Scope is now broadly reduced. This PR: - Converts remaining instances of old plan names to new plan names. In most cases, I replaced old plan names with new plan names directly. In some cases, sentences were rewritten to make a bit more sense or be more maintainable in the future. - Removes previously added preprocessor variables from Docusaurus configuration. - Update Vale styles or various artifacts of content based on linter findings. ## Review guide <!-- 1. `x.py` 2. `y.py` --> Spot check updated pages to ensure plan names appear appropriately. It's probably not necessary to check every single instance in detail. For Platform docs, changes only apply to the Next/Cloud version. After merging, I'll regenerate 2.0 docs based on this. 1.8 and before won't be updated. ## User Impact <!-- * What is the end result perceived by the user? * If there are negative side effects, please list them. --> People can see correct plan names in docs content. ## Can this PR be safely reverted and rolled back? <!-- * If unsure, leave it blank. --> - [x] YES 💚 - [ ] NO ❌ --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
1.6 KiB
1.6 KiB
products
| products |
|---|
| oss-* |
Breaking change list
Occasionally, new versions of Airbyte introduce breaking changes. This page inventories breaking changes between versions and any necessary steps to mitigate the change.
When you upgrade your Self-Managed instance of Airbyte to a version with a breaking change, you may need to take mitigating action. If you are upgrading multiple versions at once, complete the mitigaton steps for the versions you are skipping as well.
Core
1.8.x to 2.0.x
- If you deploy with abctl, version 2.0 requires abctl version 0.30.2 or later. Upgrade to version 0.30.2 or later before deploying Airbyte version 2.0.
1.7.x to 1.8.x
- Airbyte no longer publishes a
webappimage and it's no longer independently deployable. To mitigate this, complete 1.7 ingress update.
1.6.x to 1.7.x
- Airbyte began removing the
webappservice and moving its functions toserver. To mitigate this, update your ingress
Self-Managed Enterprise
1.7.x to 1.8.x
- Airbyte no longer publishes a
webappimage and it's no longer independently deployable. To mitigate this, complete 1.7 ingress update.
1.6.x to 1.7.x
- Airbyte began removing the
webappservice and moving its functions toserver. To mitigate this, update your ingress.
1.5.x to 1.6.x
- Service accounts require a new permission. Update your service account