Repository: expo/expo
File: docs/public/static/schemas/unversioned/eas-json-build-common-schema.js (JavaScript)

Code before:
export default [
  {
    name: 'withoutCredentials',
    type: 'boolean',
    description: [
      "When set to `true`, EAS CLI won't require you to configure credentials when building the app. This comes in handy when using EAS Build custom builds",
    ],
  },
  {
    name: 'extends',
    type: 'string',
    description: [
      "The name of the build profile that the current one should inherit values from. This value can't be specified per platform.",
    ],
  },
  {
    name: 'credentialsSource',
    enum: ['local', 'remote'],
    description: [
      'The source of credentials used to sign the application archive.',
      ' - `local` - if you want to provide your own `credentials.json` file. ([Learn more on this here](/app-signing/local-credentials).)',
      ' - `remote` - if you want to use the credentials managed by EAS (this is the default option).',
    ],
  },
  {
    name: 'releaseChannel',
    type: 'string',
    description: [
      '**Deprecated**: Name of the release channel for the Classic Updates service, which is only supported in SDK 49 and lower. If you do not specify a channel, your binary will pull releases from the `default` channel.',
      '',
      'EAS Update uses the [channel](#channel) field, so you can remove [releaseChannel](#releasechannel) after migrating to EAS Update. [Learn more about migrating from Classic Updates to EAS Update](/eas-update/migrate-from-classic-updates/).',

Review comment (security):
```suggestion
      "When set to `true`, EAS CLI won't require you to configure credentials when building the app. This comes in handy when using EAS Build [custom builds](/custom-builds/get-started/).",
```

Let's also add an internal link here.

Code after:
export default [
  {
    name: 'withoutCredentials',
    type: 'boolean',
    description: [
      "When set to `true`, EAS CLI won't require you to configure credentials when building the app. This comes in handy when using EAS Build [custom builds](/custom-builds/get-started/).",
    ],
  },
  {
    name: 'extends',
    type: 'string',
    description: [
      "The name of the build profile that the current one should inherit values from. This value can't be specified per platform.",
    ],
  },
  {
    name: 'credentialsSource',
    enum: ['local', 'remote'],
    description: [
      'The source of credentials used to sign the application archive.',
      ' - `local` - if you want to provide your own `credentials.json` file. ([Learn more on this here](/app-signing/local-credentials).)',
      ' - `remote` - if you want to use the credentials managed by EAS (this is the default option).',
    ],
  },
  {
    name: 'releaseChannel',
    type: 'string',
    description: [
      '**Deprecated**: Name of the release channel for the Classic Updates service, which is only supported in SDK 49 and lower. If you do not specify a channel, your binary will pull releases from the `default` channel.',
      '',
      'EAS Update uses the [channel](#channel) field, so you can remove [releaseChannel](#releasechannel) after migrating to EAS Update. [Learn more about migrating from Classic Updates to EAS Update](/eas-update/migrate-from-classic-updates/).',