Skip to content

Commit

Permalink
[eas-json] add Xcode 15.3 image (#2312)
Browse files Browse the repository at this point in the history 
* [eas-json] add Xcode 15.3 image

* update CHANGELOG.md

* fix changelog
  • Loading branch information
@szdziedzic
szdziedzic authored Apr 5, 2024
1 parent b52145c commit f62a8ca
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 68 deletions.
7 changes: 3 additions & 4 deletions CHANGELOG.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,16 +9,15 @@ This is the log of notable changes to EAS CLI and related packages.
### 🎉 New features

- Generate metadata file for project archive ([#2149](https://github.com/expo/eas-cli/pull/2149) by [@khamilowicz](https://github.com/khamilowicz))

- Add --verbose-fastlane flag to eas submit command for more robust fastlane pilot logs. ([#2276](https://github.com/expo/eas-cli/pull/2276) by [@khamilowicz](https://github.com/khamilowicz))

- Add `eas credentials:configure-build` subcommand.
([#2282](https://github.com/expo/eas-cli/pull/2282) by [@fiberjw](https://github.com/fiberjw))
- Add `eas credentials:configure-build` subcommand. ([#2282](https://github.com/expo/eas-cli/pull/2282) by [@fiberjw](https://github.com/fiberjw))

### 🐛 Bug fixes

### 🧹 Chores

- Add info about the Xcode 15.3 image to `eas.schema.json`. ([#2312](https://github.com/expo/eas-cli/pull/2312) by [@szdziedzic](https://github.com/szdziedzic))

## [7.6.2](https://github.com/expo/eas-cli/releases/tag/v7.6.2) - 2024-03-27

### 🧹 Chores
Expand Down
79 changes: 15 additions & 64 deletions packages/eas-json/schema/eas.schema.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -24,19 +24,14 @@
"version": {
"type": "string",
"description": "The compatible versions of EAS CLI with this config",
"examples": [
">=0.54.1"
]
"examples": [">=0.54.1"]
},
"requireCommit": {
"type": "boolean",
"description": "If all changes required to be committed before building or submitting"
},
"appVersionSource": {
"enum": [
"local",
"remote"
],
"enum": ["local", "remote"],
"markdownDescription": "Version policy defines whether version of your app should be based on your local project or values stored on EAS servers (remote).\n\nThis is the configuration required for `eas build:version:set` and works with the `autoIncrement` options per platform.",
"markdownEnumDescriptions": [
"When using local, the `autoIncrement` is based on your local project values.",
Expand Down Expand Up @@ -107,10 +102,7 @@
"description": "The name of the build profile that the current one should inherit values from. This value can't be specified per platform."
},
"credentialsSource": {
"enum": [
"remote",
"local"
],
"enum": ["remote", "local"],
"description": "The source of credentials used to sign build artifacts. Learn more: https://docs.expo.dev/app-signing/local-credentials/",
"markdownDescription": "The source of credentials used to sign build artifacts.\n\n- `remote` - if you want to use the credentials managed by EAS.\n- `local` - if you want to provide your own `credentials.json` file. [learn more](https://docs.expo.dev/app-signing/local-credentials/)",
"default": "remote",
Expand All @@ -132,10 +124,7 @@
"markdownDescription": "The channel is a name we can give to multiple builds to identify them easily. [Learn more](https://docs.expo.dev/eas-update/how-eas-update-works/)\n\n**This field only applies to the EAS Update service**, if your project still uses Classic Updates then use the [releaseChannel](https://docs.expo.dev/build-reference/eas-json/#releasechannel) field instead."
},
"distribution": {
"enum": [
"internal",
"store"
],
"enum": ["internal", "store"],
"description": "The method of distributing your app. Learn more: https://docs.expo.dev/build/internal-distribution/",
"markdownDescription": "The method of distributing your app.\n\n- `internal` - with this option you'll be able to share your build URLs with anyone, and they will be able to install the builds to their devices straight from the Expo website. When using `internal`, make sure the build produces an APK or IPA file. Otherwise, the shareable URL will be useless. [Learn more](https://docs.expo.dev/build/internal-distribution/)\n- `store` - produces builds for store uploads, your build URLs won't be shareable.",
"markdownEnumDescriptions": [
Expand Down Expand Up @@ -214,11 +203,7 @@
"default": "default",
"anyOf": [
{
"enum": [
"default",
"medium",
"large"
]
"enum": ["default", "medium", "large"]
},
{
"type": "string"
Expand Down Expand Up @@ -282,11 +267,7 @@
"default": "default",
"anyOf": [
{
"enum": [
"default",
"medium",
"large"
]
"enum": ["default", "medium", "large"]
},
{
"type": "string"
Expand All @@ -298,12 +279,7 @@
"description": "The version of Android NDK."
},
"autoIncrement": {
"enum": [
false,
true,
"versionCode",
"version"
],
"enum": [false, true, "versionCode", "version"],
"description": "Controls how EAS CLI bumps your application build version.",
"markdownDescription": "Controls how EAS CLI bumps your application build version.\n\nAllowed values:\n- `\"version\"` - bumps the patch of `expo.version` (e.g. `1.2.3` -> `1.2.4`).\n- `\"versionCode\"` (or `true`) - bumps `expo.android.versionCode` (e.g. `3` -> `4`).\n- `false` - versions won't be bumped automatically (default)\n\nIn the case of a bare project, it also updates versions in native code. `expo.version` corresponds to `versionName` and `expo.android.versionCode` to `versionCode` in the `build.gradle`. Google Play uses these values to identify the app build, `versionName` is the version visible to users, whereas `versionCode` defines the version number. The combination of those needs to be unique, so you can bump either of them.\n\nThis feature is not intended for use with dynamic configuration (app.config.js). EAS CLI will throw an error if you don't use app.json.",
"default": false,
Expand All @@ -315,10 +291,7 @@
]
},
"buildType": {
"enum": [
"app-bundle",
"apk"
],
"enum": ["app-bundle", "apk"],
"description": "Type of the artifact you want to build.",
"markdownDescription": "Type of the artifact you want to build. It controls what Gradle task will be used, can be overridden by `gradleCommand` or `developmentClient: true` option.\n- `app-bundle` - `:app:bundleRelease`\n- `apk` - `:app:assembleRelease`",
"markdownEnumDescriptions": [
Expand Down Expand Up @@ -365,22 +338,14 @@
"default": false
},
"enterpriseProvisioning": {
"enum": [
"universal",
"adhoc"
],
"enum": ["universal", "adhoc"],
"markdownDescription": "Provisioning method used for `\"distribution\": \"internal\"` when you have an Apple account with Apple Developer Enterprise Program membership.\n\nYou can choose if you want to use `adhoc` or `universal` provisioning. The latter is recommended as it does not require you to register each individual device. If you don't provide this option and you still authenticate with an enterprise team, you'll be prompted which provisioning method to use.",
"markdownEnumDescriptions": [
"Recommended as it does not require you to register each individual device"
]
},
"autoIncrement": {
"enum": [
false,
true,
"buildNumber",
"version"
],
"enum": [false, true, "buildNumber", "version"],
"description": "Controls how EAS CLI bumps your application build version.",
"markdownDescription": "Controls how EAS CLI bumps your application build version.\n\nAllowed values:\n\n- `\"version\"` - bumps the patch of `expo.version` (e.g. `1.2.3` -> `1.2.4`).\n- `\"buildNumber\"` (or `true`) - bumps the last component of `expo.ios.buildNumber` (e.g. `1.2.3.39` -> `1.2.3.40`).\n- `false` - versions won't be bumped automatically (default)\n\nIn the case of a bare project, it also updates versions in native code. `expo.version` corresponds to `CFBundleShortVersionString` and `expo.ios.buildNumber` to `CFBundleVersion` in the `Info.plist`. The App Store is using those values to identify the app build, `CFBundleShortVersionString` is the version visible to users, whereas `CFBundleVersion` defines the build number. The combination of those needs to be unique, so you can bump either of them.\n\nThis feature is not intended for use with dynamic configuration (app.config.js). EAS CLI will throw an error if you don't use app.json.",
"default": false,
Expand All @@ -400,6 +365,7 @@
"enum": [
"default",
"latest",
"macos-sonoma-14.4-xcode-15.3",
"macos-ventura-13.6-xcode-15.2",
"macos-ventura-13.6-xcode-15.1",
"macos-ventura-13.6-xcode-15.0",
Expand All @@ -411,7 +377,7 @@
],
"markdownEnumDescriptions": [
"`macos-ventura-13.4-xcode-14.3.1`",
"`macos-ventura-13.6-xcode-15.2`"
"`macos-sonoma-14.4-xcode-15.3`"
]
},
{
Expand All @@ -435,12 +401,7 @@
"default": "default",
"anyOf": [
{
"enum": [
"default",
"medium",
"large",
"m-medium"
]
"enum": ["default", "medium", "large", "m-medium"]
},
{
"type": "string"
Expand Down Expand Up @@ -524,12 +485,7 @@
"markdownDescription": "Path to the JSON file with service account key used to authenticate with Google Play. [Learn more](https://expo.fyi/creating-google-service-account)"
},
"track": {
"enum": [
"beta",
"alpha",
"internal",
"production"
],
"enum": ["beta", "alpha", "internal", "production"],
"description": "The track of the application to use. Learn more: https://support.google.com/googleplay/android-developer/answer/9859348?hl=en",
"markdownDescription": "The [track of the application](https://support.google.com/googleplay/android-developer/answer/9859348?hl=en) to use.",
"markdownEnumDescriptions": [
Expand All @@ -540,12 +496,7 @@
]
},
"releaseStatus": {
"enum": [
"draft",
"inProgress",
"halted",
"completed"
],
"enum": ["draft", "inProgress", "halted", "completed"],
"description": "The status of a release. Learn more: https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks",
"markdownDescription": "The status of a release. [Learn more](https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks)",
"enumDescriptions": [
Expand Down

0 comments on commit f62a8ca

Please sign in to comment.