Merge branch 'develop' into feature/vpc-assigned-linodes-table-header

docs/development-guide/05-fetching-data.md

@@ -253,7 +253,7 @@ Note: the legacy `scrollErrorIntoView` is deprecated in favor of `scrollErrorInt
 
 Since Cloud Manager uses different ways of handling forms and validation, the `scrollErrorIntoViewV2` util should be implemented using the following patterns to ensure consistency.
 
-##### Formik
+##### Formik (deprecated)
 ```Typescript
 import * as React from 'react';
 

docs/development-guide/09-mocking-data.md

@@ -41,6 +41,8 @@ const linodeList = linodeFactory.buildList(10, { region: "eu-west" });
 // [{ id: 3, label: 'linode-3', region: 'eu-west' }, ...9 more ]
 ```
 
+Because our factories are used by our dev tools, unit tests, and end-to-end tests, we should avoid creating factories with random or unpredictable default values (e.g. by using utilities like `pickRandom` to assign property values).
+
 ### Intercepting Requests
 
 The [Mock Service Worker](https://mswjs.io/) package intercepts requests at the network level and returns the response you defined in the relevant factory.

docs/development-guide/15-composition.md

@@ -0,0 +1,54 @@
+# Composition
+
+## Page Composition
+Composing pages in Cloud Manager is a multi-step process that involves several components and patterns. It usually involves using a combination of components already available to the developer, and organized according to the desired layout.
+
+It is best to avoid one off components for pages, or an excessive amount of custom CSS. It is likely that a component already exists to handle the desired layout or styling. It is often a good idea to spend some time looking through the codebase, at [storybook](https://design.linode.com/) or an existing feature of Cloud Manager before making certain composition decisions. It is also important to compose with markup semanticity in mind, and keep an eye on the render tree to avoid bloating the layout with unnecessary containers, wrappers etc, as well as ensuring that the page is accessible, performant, and has good test coverage. When in doubt, one can also check with the product or UX team to ensure that a component exists for the desired layout or styling.
+
+### Responsive Design
+
+While Cloud Manager layout and components are responsive out of the box, some extra handling may be needed for pages that have unique responsive requirements, or because the features has a more complex layout.
+A wide array of tools are available to help with responsive design, including media queries, CSS Grid & Flexbox, as well as the `<Hidden />` component, which can be used to hide elements at specific breakpoints.
+
+Some designs may not feature a mobile layout, and for those cases it is recommended to gather existing examples from the codebase, or from other pages that have a similar layout.
+
+## Form Composition
+
+### Formik
+Formik is now deprecated. Please use react-hook-form.
+
+### React Hook Form
+The preferred library for building forms in Cloud Manager is [react-hook-form](https://react-hook-form.com/). It is a complete set of tools for building complex forms, and is well documented.
+The general way to get started is to use the `useForm` hook, which returns a form context and a set of methods to interact with the form.
+
+```Typescript
+const methods = useForm<LinodeCreateFormValues>({
+  defaultValues,
+  mode: 'onBlur',
+  resolver: myResolvers,
+  // other methods
+});
+```
+
+`methods` is an object that contains the form context and a set of methods to interact with the form.
+It is passed to the `FormProvider` component, which is a wrapper that provides the form context to the form.
+
+```Typescript
+<FormProvider {...methods}>
+  <form onSubmit={methods.handleSubmit(onSubmit)}>
+    {/* form fields */}
+    <button type="submit">Submit</button>
+  </form>
+</FormProvider>
+```
+
+It is important to note that react-hook-form does not provide any UI components. It is the responsibility of the developer to provide the form fields and validation, as well as employing semantic markup for accessibility purposes.
+ex: a `<form>` element should have a corresponding `<button type="submit">` element to submit the form so that it is obvious to assistive technologies that the form can be submitted via keyboard.
+
+It is also important to remember to manage the form state through comprehensive context in order to avoid unnecessary rerenders.
+
+The Linode Create Page is a good example of a complex form that is built using react-hook-form, using the best practices mentioned above.
+
+### Uncontrolled Forms
+Uncontrolled forms are a type of form that does not have a state for its values. It is often used for simple forms that do not need to be controlled, such as forms with a single input field or call to action.
+

packages/api-v4/.changeset/pr-10939-upcoming-features-1726263534115.md

@@ -0,0 +1,5 @@
+---
+"@linode/api-v4": Upcoming Features
+---
+
+DBaaS V2 readonly hosts ([#10939](https://github.com/linode/manager/pull/10939))

packages/api-v4/CHANGELOG.md

@@ -1,3 +1,19 @@
+## [2024-09-16] - v0.126.0
+
+
+### Added:
+
+- LinodeCapabilities type used for `capabilities` property of Linode interface ([#10920](https://github.com/linode/manager/pull/10920))
+
+### Tech Stories:
+
+- Update vitest to latest ([#10843](https://github.com/linode/manager/pull/10843))
+
+### Upcoming Features:
+
+- Change 'bs_encryption_supported' property on Linode object to 'capabilities' ([#10837](https://github.com/linode/manager/pull/10837))
+- Add beta API root for CloudPulse endpoints ([#10851](https://github.com/linode/manager/pull/10851))
+
 ## [2024-09-03] - v0.125.0
 
 

packages/api-v4/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@linode/api-v4",
-  "version": "0.125.0",
+  "version": "0.126.0",
   "homepage": "https://github.com/linode/manager/tree/develop/packages/api-v4",
   "bugs": {
     "url": "https://github.com/linode/manager/issues"
@@ -67,7 +67,7 @@
     "lint-staged": "^15.2.9",
     "prettier": "~2.2.1",
     "tsup": "^8.2.4",
-    "vitest": "^2.0.5"
+    "vitest": "^2.1.1"
   },
   "lint-staged": {
     "*.{ts,tsx,js}": [

packages/api-v4/src/databases/databases.ts

@@ -223,11 +223,11 @@ export const getDatabaseBackup = (
   );
 
 /**
- * restoreWithBackup
+ * legacyRestoreWithBackup
  *
  * Fully restore a backup to the cluster
  */
-export const restoreWithBackup = (
+export const legacyRestoreWithBackup = (
   engine: Engine,
   databaseID: number,
   backupID: number
@@ -243,6 +243,25 @@ export const restoreWithBackup = (
     setMethod('POST')
   );
 
+/**
+ * newRestoreWithBackup for the New Database
+ *
+ * Fully restore a backup to the cluster
+ */
+export const newRestoreWithBackup = (
+  engine: Engine,
+  label: string,
+  fork: {
+    source: number;
+    restore_time?: string;
+  }
+) =>
+  Request<{}>(
+    setURL(`${API_ROOT}/databases/${encodeURIComponent(engine)}/instances`),
+    setMethod('POST'),
+    setData({ fork, label })
+  );
+
 /**
  * getDatabaseCredentials
  *

packages/api-v4/src/databases/types.ts

@@ -152,6 +152,7 @@ export interface BaseDatabase {
    */
   members: Record<string, MemberType>;
   platform?: string;
+  oldest_restore_time?: string;
 }
 
 export interface MySQLDatabase extends BaseDatabase {

packages/api-v4/src/regions/types.ts

@@ -13,7 +13,6 @@ export type Capabilities =
   | 'Kubernetes'
   | 'Linodes'
   | 'Managed Databases'
-  | 'Managed Databases Beta'
   | 'Metadata'
   | 'NodeBalancers'
   | 'Object Storage'

packages/manager/.changeset/pr-10858-changed-1725914163062.md

@@ -0,0 +1,5 @@
+---
+"@linode/manager": Changed
+---
+
+Move Region section above Images in Linode Create and update default OS to Ubuntu 24.04 LTS ([#10858](https://github.com/linode/manager/pull/10858))