By default specs are merged additively. That is for every value:
- if existing value and new value are both dictionaries merge them and continue down the hierarchy
- if existing value and new value are both an array then add the new value to the end of the array
- otherwise replace the existing value with the new value
This merging behaviour can be overridden on a value basis. If you wish to replace a whole value (set a new dictionary or new array instead of merging them) then just affix :REPLACE to the key

Note that target names can also be changed by adding a name property to a target.
Options  Copy Section
- [ ] minimumXcodeGenVersion: String - The minimum version of XcodeGen required.
- [ ] carthageBuildPath: String - The path to the carthage build directory. Defaults to Carthage/Build. This is used when specifying target carthage dependencies
- [ ] carthageExecutablePath: String - The path to the carthage executable. Defaults to carthage. You can specify when you use custom built or locally installed Carthage using Mint, for example.
- [ ] createIntermediateGroups: Bool - If this is specified and set to true, then intermediate groups will be created for every path component between the folder containing the source and next existing group it finds or the base path. For example, when enabled if a source path is specified as Vendor/Foo/Hello.swift, the group Vendor will created as a parent of the Foo group. This can be overridden in a specific Target source
- [ ] bundleIdPrefix: String - If this is specified then any target that doesn't have an PRODUCT_BUNDLE_IDENTIFIER (via all levels of build settings) will get an autogenerated one by combining bundleIdPrefix and the target name: bundleIdPrefix.name. The target name will be stripped of all characters that aren't alphanumerics, hyphens, or periods. Underscores will be replaced with hyphens.
- [ ] settingPresets: String - This controls the settings that are automatically applied to the project and its targets. These are the same build settings that Xcode would add when creating a new project. Project settings are applied by config type. Target settings are applied by the product type and platform. By default this is set to all
	- all: project and target settings
	- project: only project settings
	- targets: only target settings
	- none: no settings are automatically applied
- [ ] developmentLanguage: String - Sets the development language of the project. Defaults to en
- [ ] usesTabs: Bool - If this is specified, the Xcode project will override the user's setting determining whether or not tabs or spaces should be used in the project.
- [ ] indentWidth: Int - If this is specified, the Xcode project will override the user's setting for indent width in number of spaces.
- [ ] tabWidth: Int - If this is specified, the Xcode project will override the user's setting for indent width in number of spaces.
- [ ] xcodeVersion: String - The version of Xcode. This defaults to the latest version periodically. You can specify it in the format 0910 or 9.1
- [ ] projectFormat: String - The version of Xcode project. By default this is set to xcode16_0
  - xcode16_3: Xcode 16.3
  - xcode16_0: Xcode 16.0
  - xcode15_3: Xcode 15.3
  - xcode15_0: Xcode 15.0
  - xcode14_0: Xcode 14.0
- [ ] deploymentTarget: [Platform: String] - A project wide deployment target can be specified for each platform otherwise the default SDK version in Xcode will be used. This will be overridden by any custom build settings that set the deployment target eg IPHONEOS_DEPLOYMENT_TARGET. Target specific deployment targets can also be set with Target.deploymentTarget.
- [ ] disabledValidations: [String] - A list of validations that can be disabled if they're too strict for your use case. By default this is set to an empty array. Currently these are the available options:
  - missingConfigs: Disable errors for configurations in yaml files that don't exist in the project itself. This can be useful if you include the same yaml file in different projects
  - missingConfigFiles: Disable checking for the existence of configuration files. This can be useful for generating a project in a context where config files are not available.
  - missingTestPlans: Disable checking if test plan paths exist. This can be useful if your test plans haven't been created yet.
- [ ] defaultConfig: String - The default configuration for command line builds from Xcode. If the configuration provided here doesn't match one in your configs key, XcodeGen will fail. If you don't set this, the first configuration alphabetically will be chosen.
- [ ] groupSortPosition: String - Where groups are sorted in relation to other files. Either:
  - none - sorted alphabetically with all the other files
  - top - at the top, before files
  - bottom (default) - at the bottom, after other files
- [ ] groupOrdering: [[GroupOrdering]](#groupOrdering) - An order of groups.
- [ ] transitivelyLinkDependencies: Bool - If this is true then targets will link to the dependencies of their target dependencies. If a target should embed its dependencies, such as application and test bundles, it will embed these transitive dependencies as well. Some complex setups might want to set this to false and explicitly specify dependencies at every level. Targets can override this with Target.transitivelyLinkDependencies. Defaults to false.
- [ ] generateEmptyDirectories: Bool - If this is true then empty directories will be added to project too else will be missed. Defaults to false.
- [ ] findCarthageFrameworks: Bool - When this is set to true, all the individual frameworks for Carthage framework dependencies will automatically be found. This property can be overridden individually for each carthage dependency - for more details see See findFrameworks in the Dependency section. Defaults to false.
- [ ] localPackagesGroup: String - The group name that local packages are put into. This defaults to Packages. Use "" to specify the project root.
- [ ] fileTypes: String: [FileType] - A list of default file options for specific file extensions across the project. Values in Sources will overwrite these settings.
- [ ] preGenCommand: String - A bash command to run before the project has been generated. If the project isn't generated due to no changes when using the cache then this won't run. This is useful for running things like generating resources files before the project is regenerated.
- [ ] postGenCommand: String - A bash command to run after the project has been generated. If the project isn't generated due to no changes when using the cache then this won't run. This is useful for running things like pod install only if the project is actually regenerated.
- [ ] useBaseInternationalization: Bool If this is false and your project does not include resources located in a Base.lproj directory then Base will not be included in the projects 'known regions'. The default value is true. 
- [ ] schemePathPrefix: String - A path prefix for relative paths in schemes, such as StoreKitConfiguration. The default is "../../", which is suitable for non-workspace projects. For use in workspaces, use "../".
- [ ] defaultSourceDirectoryType: String - When a Target source doesn't specify a type and is a directory, this is the type that will be used. If nothing is specified for either then group will be used.
  - group (default)
  - folder
  - syncedFolder: Can be used starting from projectFormat xcode16_0

GroupOrdering  Copy Section
Describe an order of groups. Available parameters:
- [ ] pattern: String - A group name pattern. Can be just a single string and also can be a regex pattern. Optional option, if you don't set it, it will pattern for the main group, i.e. the project.
- [ ] order: [String] - An order of groups.

In this example, we set up the order of two groups. First one is the main group, i.e. the project, note that in this case, we shouldn't set pattern option and the second group order is for groups whose names ends with Screen.
FileType  Copy Section

Default settings for file extensions. See Sources for more documentation on properties. If you overwrite an extension that XcodeGen already provides by default, you will need to provide all the settings.
- [ ] file: Bool - Whether this extension should be treated like a file. Defaults to true.
- [ ] buildPhase: String - The default build phase.
- [ ] attributes: [String] - Additional settings attributes that will be applied to any build files.
- [ ] resourceTags: [String] - On Demand Resource Tags that will be applied to any resources. This also adds to the project attribute's knownAssetTags.
- [ ] compilerFlags: [String] - A list of compiler flags to add.
Breakpoints  Copy Section
- [x] type: String - Breakpoint type
    - File: file breakpoint
    - Exception: exception breakpoint
    - SwiftError: swift error breakpoint
    - OpenGLError: OpenGL breakpoint
    - Symbolic: symbolic breakpoint
    - IDEConstraintError: IDE constraint breakpoint
    - IDETestFailure: IDE test failure breakpoint
    - RuntimeIssue: Runtime issue breakpoint
- [ ] enabled: Bool - Indicates whether it should be active. Default to true
- [ ] ignoreCount: Int - Indicates how many times it should be ignored before stopping, Default to 0
- [ ] continueAfterRunningActions: Bool - Indicates if should automatically continue after evaluating actions, Default to false
- [ ] path: String - Breakpoint file path (only required by file breakpoints)
- [ ] line: Int - Breakpoint line (only required by file breakpoints)
- [ ] symbol: String - Breakpoint symbol (only used by symbolic breakpoints)
- [ ] module: String - Breakpoint module (only used by symbolic breakpoints)
- [ ] scope: String - Breakpoint scope (only used by exception breakpoints)
    - All
    - Objective-C (default)
    - C++
- [ ] stopOnStyle: String - Indicates if should stop on style (only used by exception breakpoints)
    -throw (default)
    -catch
- [ ] condition: String - Breakpoint condition
- [ ] actions: [Breakpoint Action] - breakpoint actions

#### Breakpoint Action
- [x] type: String - Breakpoint action type
    - DebuggerCommand: execute debugger command
    - Log: log message
    - ShellCommand: execute shell command
    - GraphicsTrace: capture GPU frame
    - AppleScript: execute AppleScript
    - Sound: play sound
- [ ] command: String - Debugger command (only used by debugger command breakpoint action)
- [ ] message: String - Log message (only used log message breakpoint action)
- [ ] conveyanceType: String - Conveyance type (only used by log message breakpoint action)
    - console: log message to console (default)
    - speak: speak message
- [ ] path: String - Shell command file path (only used by shell command breakpoint action)
- [ ] arguments: String - Shell command arguments (only used by shell command breakpoint action)
- [ ] waitUntilDone: Bool - Indicates whether it should wait until done (only used by shell command breakpoint action). Default to false
- [ ] script: String - AppleScript (only used by AppleScript breakpoint action)
- [ ] sound: String - Sound name (only used by sound breakpoint action)
    - Basso (default)
    - Blow
    - Bottle
    - Frog
    - Funk
    - Glass
    - Hero
    - Morse
    - Ping
    - Pop
    - Purr
    - Sosumi
    - Submarine
    - Tink

Configs  Copy Section
Each config maps to a build type of either debug or release which will then apply default Build Settings to the project. Any value other than debug or release (for example none), will mean no default Build Settings will be applied to the project.

If no configs are specified, default Debug and Release configs will be created automatically.
Setting Groups  Copy Section
Setting groups are named groups of Build Settings that can be reused elsewhere. Each preset is a Settings schema, so can include other groups  or define settings by configs.

Settings  Copy Chapter
Settings correspond to Build Settings tab in Xcode. To display Setting Names instead of Setting Titles, select Editor -> Show Setting Names in Xcode.
Settings can either be a simple map of Build Settings [String:String], or can be more advanced with the following properties:
- [ ] groups: [String] - List of Setting Groups to include and merge
- [ ] configs: String:[Settings] - Mapping of config name to a settings spec. These settings will only be applied for that config. Each key will be matched to any configs that contain the key and is case insensitive. So if you had Staging Debug and Staging Release, you could apply settings to both of them using staging. However if a config name is an exact match to a config it won't be applied to any others. eg Release will be applied to config Release but not Staging Release
- [ ] base: [String:String] - Used to specify default settings that apply to any config

Don't mix simple maps with groups, base and configs.
If groups, base, configs are used then simple maps is silently ignored.
In this example, CURRENT_PROJECT_VERSION will be set, but MARKETING_VERSION will be ignored:

Settings are merged in the following order: groups, base, configs (simple maps are ignored).
Target  Copy Chapter
- [x] type: Product Type - Product type of the target
- [x] platform: Platform - Platform of the target
- [ ] supportedDestinations: [Supported Destinations] - List of supported platform destinations for the target.
- [ ] deploymentTarget: String - The deployment target (eg 9.2). If this is not specified the value from the project set in Options.deploymentTarget.PLATFORM will be used.
- [ ] sources: Sources - Source directories of the target
- [ ] configFiles: Config Files - .xcconfig files per config
- [ ] settings: Settings - Target specific build settings. Default platform and product type settings will be applied first before any custom settings defined here. Other context dependant settings will be set automatically as well:
	- INFOPLIST_FILE: If it doesn't exist your sources will be searched for Info.plist files and the first one found will be used for this setting
	- FRAMEWORK_SEARCH_PATHS: If carthage framework dependencies are used, the platform build path will be added to this setting
	- OTHER_LDFLAGS:  See requiresObjCLinking below
  - TEST_TARGET_NAME: for ui tests that target an application
  - TEST_HOST: for unit tests that target an application
- [ ] dependencies: [Dependency] - Dependencies for the target
- [ ] info: Plist - If defined, this will generate and write an Info.plist to the specified path and use it by setting the INFOPLIST_FILE build setting for every configuration, unless INFOPLIST_FILE is already defined in  settings for this configuration. The following properties are generated automatically if appropriate, the rest will have to be provided.
  - CFBundleIdentifier
  - CFBundleInfoDictionaryVersion
  - CFBundleExecutable Not generated for targets of type bundle
  - CFBundleName
  - CFBundleDevelopmentRegion
  - CFBundleShortVersionString
  - CFBundleVersion
  - CFBundlePackageType
- [ ] entitlements: Plist - If defined this will generate and write a .entitlements file, and use it by setting CODE_SIGN_ENTITLEMENTS build setting for every configuration. All properties must be provided
- [ ] templates: [String] - A list of Target Templates referenced by name that will be merged with the target in order. Any instances of ${target_name} within these templates will be replaced with the target name.
- [ ] templateAttributes: [String: String] - A list of attributes where each instance of ${attributeName} within the templates listed in templates will be replaced with the value specified.
- [ ] transitivelyLinkDependencies: Bool - If this is not specified the value from the project set in Options.transitivelyLinkDependencies will be used.
- [ ] directlyEmbedCarthageDependencies: Bool - If this is true Carthage framework dependencies will be embedded using an Embed Frameworks build phase instead of the copy-frameworks script. Defaults to true for all targets except iOS/tvOS/watchOS Applications.
- [ ] requiresObjCLinking: Bool - If this is true any targets that link to this target will have -ObjC added to their OTHER_LDFLAGS. This is required if a static library has any categories or extensions on Objective-C code. See this guide for more details. Defaults to true if type is library.static. If you are 100% sure you don't have categories or extensions on Objective-C code (pure Swift with no use of Foundation/UIKit) you can set this to false, otherwise it's best to leave it alone.
- [ ] onlyCopyFilesOnInstall: Bool – If this is true, the Embed Frameworks and Embed App Extensions (if available) build phases will have the "Copy only when installing" chekbox checked. Defaults to false.
- [ ] buildToolPlugins: [Build Tool Plug-ins] - Commands for the build system that run automatically during the build.
- [ ] preBuildScripts: [Build Script] - Build scripts that run before any other build phases
- [ ] postCompileScripts: [Build Script] - Build scripts that run after the Compile Sources phase
- [ ] postBuildScripts: [Build Script] - Build scripts that run after any other build phases
- [ ] buildRules: [Build Rule] - Custom build rules
- [ ] scheme: Target Scheme - Generated scheme with tests or config variants
- [ ] legacy: Legacy Target - When present, opt-in to make an Xcode "External Build System" legacy target instead.
- [ ] attributes: [String: Any] - This sets values in the project TargetAttributes. It is merged with attributes from the project and anything automatically added by XcodeGen, with any duplicate values being override by values specified here. This is for advanced use only. Properties that are already set include:
	- DevelopmentTeam: if all configurations have the same DEVELOPMENT_TEAM setting
	- ProvisioningStyle: if all configurations have the same CODE_SIGN_STYLE setting
	- TestTargetID: if all configurations have the same TEST_TARGET_NAME setting
- [ ] putResourcesBeforeSourcesBuildPhase: Bool - If this is true the Copy Resources step will be placed before the Compile Sources build step.
Product Type  Copy Section
This will provide default build settings for a certain product type. It can be any of the following:
- application
- application.on-demand-install-capable
- application.messages
- application.watchapp
- application.watchapp2
- application.watchapp2-container
- app-extension
- app-extension.intents-service
- app-extension.messages
- app-extension.messages-sticker-pack
- bundle
- bundle.ocunit-test
- bundle.ui-testing
- bundle.unit-test
- extensionkit-extension
- framework
- instruments-package
- library.dynamic
- library.static
- framework.static
- tool
- tv-app-extension
- watchkit-extension
- watchkit2-extension
- xcode-extension
- driver-extension
- system-extension
- xpc-service
- "" (used for legacy targets)
Platform  Copy Section
This will provide default build settings for a certain platform. It can be any of the following:
- auto (available only when we use supportedDestinations)
- iOS
- tvOS
- macOS
- watchOS
- visionOS (visionOS doesn't support Carthage usage)
Note that when we use supported destinations with Xcode 14+ we can avoid the definition of platform that fallbacks to the auto value.
Multi Platform targets
You can also specify an array of platforms. This will generate a target for each platform.
If deploymentTarget is specified for a multi platform target, it can have different values per platform similar to how it's defined in Options. See below for an example.
If you reference the string ${platform} anywhere within the target spec, that will be replaced with the platform.
The generated targets by default will have a suffix of _${platform} applied, you can change this by specifying a platformSuffix or platformPrefix.
If no PRODUCT_NAME build setting is specified for a target, this will be set to the target name, so that this target can be imported under a single name.

The above will generate 2 targets named MyFramework_iOS and MyFramework_tvOS, with all the relevant platform build settings. They will both have a PRODUCT_NAME of MyFramework
Supported Destinations  Copy Section
This will provide a mix of default build settings for the chosen platform destinations. It can be any of the following:
- iOS
- tvOS
- macOS
- macCatalyst
- visionOS
- watchOS

Note that the definition of supported destinations can be applied to almost every type of bundle making everything more easy to manage (app targets, unit tests, UI tests etc). App targets currently do not support the watchOS destination. Create a separate target using platform for watchOS apps. See Apple's Configuring a multiplatform app for details.
Sources  Copy Section
Specifies the source directories for a target. This can either be a single source or a list of sources. Applicable source files, resources, headers, and .lproj files will be parsed appropriately.
A source can be provided via a string (the path) or an object of the form:
#### Target Source
- [x] path: String - The path to the source file or directory.
- [ ] name: String - Can be used to override the name of the source file or directory. By default the last component of the path is used for the name
- [ ] group: String - Can be used to override the parent group of the source file or directory. By default a group is created at the root with the name of this source file or directory or intermediate groups are created if createIntermediateGroups is set to true. Multiple groups can be created by separating each one using a /. If multiple target sources share the same group, they will be put together in the same parent group.
- [ ] compilerFlags: [String] or String - A list of compilerFlags to add to files under this specific path provided as a list or a space delimited string. Defaults to empty.
- [ ] excludes: [String] - A list of global patterns) representing the files to exclude. These rules are relative to path and _not the directory where project.yml resides_. XcodeGen uses Bash 4's Glob behaviors where globstar () is enabled.
- [ ] includes: [String] - A list of global patterns in the same format as excludes representing the files to include. These rules are relative to path and _not the directory where project.yml resides_. If excludes is present and file conflicts with includes, excludes will override the includes behavior.
- [ ] explicitFolders: [String] - Only valid for syncedFolder type. A list of global patterns in the same format as excludes to child folders that Xcode should treat as folder references.
- [ ] destinationFilters: [Supported Destinations] - List of supported platform destinations the files should filter to. Defaults to all supported destinations.
- [ ] inferDestinationFiltersByPath: Bool - This is a convenience filter that helps you to filter the files if their paths match these patterns /<supportedDestination>/ or _<supportedDestination>.swift. Note, if you use destinationFilters this flag will be ignored.
- [ ] createIntermediateGroups: Bool - This overrides the value in Options.
- [ ] optional: Bool - Disable missing path check. Defaults to false.
- [ ] buildPhase: String - This manually sets the build phase this file or files in this directory will be added to, otherwise XcodeGen will guess based on the file extension. Note that Info.plist files will never be added to any build phases, no matter what this setting is. Possible values are:
	- sources - Compile Sources phase
	- resources - Copy Bundle Resources phase
	- headers - Headers Phase
	- copyFiles - Copy Files Phase. Must be specified as an object with the following fields:
		- [x] destination: String - Destination of the Copy Files phase. This can be one of the following values:
			- absolutePath
			- productsDirectory
			- wrapper
			- executables
			- resources
			- javaResources
			- frameworks
			- sharedFrameworks
			- sharedSupport
			- plugins
		- [ ] subpath: String - The path inside of the destination to copy the files.
	- none - Will not be added to any build phases
- [ ] type: String: This can be one of the following values
	- file: a file reference with a parent group will be created (Default for files or directories with extensions)
	- group: a group with all it's containing files. (Default for directories without extensions)
	- folder: a folder reference.
	- syncedFolder: Xcode 16's synchronized folders, also knows as buildable folders
- [ ] headerVisibility: String - The visibility of any headers. This defaults to public, but can be either:
	- public
	- private
	- project
- [ ] attributes: [String] - Additional settings attributes that will be applied to any build files.
- [ ] resourceTags: [String] - On Demand Resource Tags that will be applied to any resources. This also adds to the project attribute's knownAssetTags

Dependency  Copy Section
A dependency can be one of a 6 types:
- target: name - links to another target. If you are using project references you can specify a target within another project by using ProjectName/TargetName for the name
- framework: path - links to a framework or XCFramework
- carthage: name - helper for linking to a Carthage framework (not XCFramework)
- sdk: name - links to a dependency with the SDK. This can either be a relative path within the sdk root or a single filename that references a framework (.framework) or lib (.tbd)
- package: name - links to a Swift Package. The name must match the name of a package defined in the top level packages
- bundle: name - adds the pre-built bundle for the supplied name to the copy resources build phase. This is useful when a dependency exists on a static library target that has an associated bundle target, both existing in a separate project. Only usable in target types which can copy resources.
Linking options:
- [ ] embed: Bool - Whether to embed the dependency. Defaults to true for application target and false for non application targets.
- [ ] link: Bool - Whether to link the dependency. Defaults to true depending on the type of the dependency and the type of the target (e.g. static libraries will only link to executables by default).
- [ ] codeSign: Bool - Whether the codeSignOnCopy setting is applied when embedding framework. Defaults to true.
- [ ] removeHeaders: Bool - Whether the removeHeadersOnCopy setting is applied when embedding the framework. Defaults to true.
- [ ] weak: Bool - Whether the Weak setting is applied when linking the framework. Defaults to false.
- [ ] platformFilter: String - This field is specific to Mac Catalyst. It corresponds to the "Platforms" dropdown in the Frameworks & Libraries section of Target settings in Xcode. Available options are: iOS, macOS and all. Defaults is all.
- [ ] destinationFilters: [Supported Destinations] - List of supported platform destinations this dependency should filter to. Defaults to all supported destinations.
- [ ] platforms: [Platform] - List of platforms this dependency should apply to. Defaults to all applicable platforms.
- copy - Copy Files Phase for this dependency. This only applies when embed is true. Must be specified as an object with the following fields:
    - [x] destination: String - Destination of the Copy Files phase. This can be one of the following values:
        - absolutePath
        - productsDirectory
        - wrapper
        - executables
        - resources
        - javaResources
        - frameworks
        - sharedFrameworks
        - sharedSupport
        - plugins
    - [ ] subpath: String - The path inside of the destination to copy the files.
Implicit Framework options:
This only applies to framework dependencies. Implicit framework dependencies are useful in Xcode Workspaces which have multiple .xcodeproj that are not embedded within each other yet have a dependency on a framework built in an adjacent .xcodeproj.  By having Find Implicit Dependencies checked within your scheme Build Options Xcode can link built frameworks in BUILT_PRODUCTS_DIR.
- [ ] implicit: Bool - Whether the framework is an implicit dependency. Defaults to false .
Carthage Dependency
- [ ] findFrameworks: Bool - Whether to find Carthage frameworks automatically. Defaults to true .
- [ ] linkType: String - Dependency link type. This value should be dynamic or static. Default value is dynamic .
Carthage frameworks are expected to be in CARTHAGE_BUILD_PATH/PLATFORM/FRAMEWORK.framework where:
 - CARTHAGE_BUILD_PATH = options.carthageBuildPath or Carthage/Build by default
 - PLATFORM = the target's platform
 - FRAMEWORK = the specified name.
 To link an XCFramework produced by Carthage (in CARTHAGE_BUILD_PATH/FRAMEWORK.xcframework), use a normal framework:
 dependency. The helper logic provided by this dependency type is not necessary.
All the individual frameworks of a Carthage dependency can be automatically found via findFrameworks: true. This overrides the value of Options.findCarthageFrameworks. Otherwise each one will have to be listed individually.
Xcodegen uses .version files generated by Carthage in order for this framework lookup to work, so the Carthage dependencies will need to have already been built at the time XcodeGen is run.
If any applications contain carthage dependencies within itself or any dependent targets, a carthage copy files script is automatically added to the application containing all the relevant frameworks. A FRAMEWORK_SEARCH_PATHS setting is also automatically added
Carthage officially supports static frameworks. In this case, frameworks are expected to be in CARTHAGE_BUILD_PATH/PLATFORM/Static/FRAMEWORK.framework.
You can specify linkType to static to integrate static ones.

SDK Dependency
- [ ] root: String - Root of framework path, for example DEVELOPER_DIR. Default value is BUILT_PRODUCTS_DIR

Package dependency
- [ ] product: String - The product to use from the package. This defaults to the package name, so is only required if a Package has multiple libraries or a library with a differing name. Use this over products when you want to define different linking options per product.
- [ ] products: String - A list of products to use from the package. This can be used when depending on multiple products from a package.

Depending on multiple products from a package:

Config Files  Copy Section
Specifies .xcconfig files for each configuration.

Plist  Copy Section

Plists are created on disk on every generation of the project. They can be used as a way to define Info.plist or .entitlement files. Some Info.plist properties are generated automatically.
- [x] path: String - This is the path where the plist will be written to
- [x] properties: [String: Any] - This is a map of all the plist keys and values

Build Tool Plug-ins  Copy Section
To add Build Tool Plug-ins, you need to add information about plugins to Target:
- buildToolPlugins: List of plugins to connect to the target
Each plugin includes information:
- [x] plugin: String - plugin name 
- [x] package: String - the name of the package that contains the plugin
Сonnect the plugin to the desired target:

Don't forget to add a package containing the plugin we need:

Build Script  Copy Section
Run script build phases can be added at 3 different points in the build:
- preBuildScripts: Before any other build phases
- postCompileScripts: After the compile sources build phase
- postBuildScripts: After any other build phases
Each script can contain:
- [x] path: String - a relative or absolute path to a shell script
- [x] script: String - an inline shell script
- [ ] name: String - name of a script. Defaults to Run Script
- [ ] inputFiles: [String] - list of input files
- [ ] outputFiles: [String] - list of output files
- [ ] inputFileLists: [String] - list of input .xcfilelist
- [ ] outputFileLists: [String] - list of output .xcfilelist
- [ ] shell: String - shell used for the script. Defaults to /bin/sh
- [ ] showEnvVars: Bool - whether the environment variables accessible to the script show be printed to the build log. Defaults to true
- [ ] runOnlyWhenInstalling: Bool - whether the script is only run when installing (runOnlyForDeploymentPostprocessing). Defaults to false
- [ ] basedOnDependencyAnalysis: Bool - whether to skip the script if inputs, context, or outputs haven't changed. Defaults to true
- [ ] discoveredDependencyFile: String - discovered dependency .d file. Defaults to none
Either a path or script must be defined, the rest are optional.
A multiline script can be written using the various YAML multiline methods, for example with | as below:

Build Rule  Copy Section
- [ ] filePattern: String - A glob pattern for the files that will have the build rule run on them. This or fileType must be defined
- [ ] fileType: String - A file type determined by Xcode. The available types can be seen by hovering your mouse of the Process dropdown in the Xcode interface. For example sourcecode.swift or file.xib. This or filePattern must be defined.
- [ ] script: String - The script that will be run on each file. This or compilerSpec must be defined.
- [ ] compilerSpec: String: A reference to a built in apple tool to run on each file. This is for advanced use and the the values for this must be checked. This or script must be defined.
- [ ] name: String - The name of a build rule. Defaults to Build Rule
- [ ] outputFiles: [String] - The list of output files
- [ ] outputFilesCompilerFlags: [String] - The list of compiler flags to apply to the output files
- [ ] runOncePerArchitecture: Bool - a boolean that indicates if this rule should run once per architecture. This defaults to true

Target Scheme  Copy Section
This is a convenience used to automatically generate schemes for a target based on different configs or included tests. If you want more control check out the top level Scheme.
- [x] configVariants: [String] - This generates a scheme for each entry, using configs that contain the name with debug and release variants. This is useful for having different environment schemes.
- [ ] testTargets: [Test Target] - a list of test targets that should be included in the scheme. These will be added to the build targets and the test entries. Each entry can either be a simple string, or a Test Target
- [ ] gatherCoverageData: Bool - a boolean that indicates if this scheme should gather coverage data. This defaults to false
- [ ] coverageTargets: [Testable Target Reference - a list of targets to gather code coverage. Each entry can either be a simple string, a string using Project Reference or Testable Target Reference
- [ ] disableMainThreadChecker: Bool - a boolean that indicates if this scheme should disable the Main Thread Checker. This defaults to false
- [ ] stopOnEveryMainThreadCheckerIssue: Bool - a boolean that indicates if this scheme should stop at every Main Thread Checker issue. This defaults to false
- [ ] disableThreadPerformanceChecker: Bool - a boolean that indicates if this scheme should disable the Thread Performance Checker. This defaults to false
- [ ] buildImplicitDependencies: Bool - Flag to determine if Xcode should build implicit dependencies of this scheme. By default this is true if not set.
- [ ] language: String - a String that indicates the language used for running and testing. This defaults to nil
- [ ] region: String - a String that indicates the region used for running and testing. This defaults to nil
- [ ] commandLineArguments: [String:Bool] - a dictionary from the argument name (String) to if it is enabled (Bool). These arguments will be added to the Test, Profile and Run scheme actions
- [ ] environmentVariables: [Environment Variable] or [String:String] - environment variables for Run, Test and Profile scheme actions. When passing a dictionary, every key-value entry maps to a corresponding variable that is enabled.
- [ ] testPlans:  [Test Plan] - List of test plan locations that will be referenced in the scheme.
- [ ] preActions: [Execution Action] - Scripts that are run before the build action
- [ ] postActions: [Execution Action] - Scripts that are run after the build action
- [ ] management: Scheme Management - Management options for the scheme
- [ ] storeKitConfiguration: String - specify storekit configuration to use during run. See Options.
For example, the spec below would create 3 schemes called:
- MyApp Test
- MyApp Staging
- MyApp Production
Each scheme would use different build configuration for the different build types, specifically debug configs for run, test, and analyze, and release configs for profile and archive.
The MyUnitTests target would also be linked.

Legacy Target  Copy Section
By providing a legacy target, you are opting in to the "Legacy Target" mode. This is the "External Build Tool" from the Xcode GUI. This is useful for scripts that you want to run as dependencies of other targets, but you want to make sure that it only runs once even if it is specified as a dependency from multiple other targets.
- [x] toolPath: String - Path to the build tool used in the legacy target.
- [ ] arguments: String - Build arguments used for the build tool in the legacy target
- [ ] passSettings: Bool - Whether or not to pass build settings down to the build tool in the legacy target.
- [ ] workingDirectory: String - The working directory under which the build tool will be invoked in the legacy target.
Aggregate Target  Copy Chapter
This is used to override settings or run build scripts in specific targets
- [x] targets: [String] - The list of target names to include as target dependencies
- [ ] configFiles: Config Files - .xcconfig files per config
- [ ] settings: Settings - Target specific build settings.
- [ ] buildToolPlugins: [Build Tool Plug-ins] - Commands for the build system that run automatically during the build
- [ ] buildScripts: [Build Script] - Build scripts to run
- [ ] scheme: Target Scheme - Generated scheme
- [ ] attributes: [String: Any] - This sets values in the project TargetAttributes. It is merged with attributes from the project and anything automatically added by XcodeGen, with any duplicate values being override by values specified here
Target Template  Copy Chapter
This is a template that can be referenced from a normal target using the templates property. The properties of this template are the same as a Target.
Any instances of ${target_name} within each template will be replaced by the final target name which references the template.
Any attributes defined within a targets templateAttributes will be used to replace any attribute references in the template using the syntax ${attribute_name}.

Scheme  Copy Chapter
Schemes allows for more control than the convenience Target Scheme on Target
- [x] build: Build options
- [ ] run: The run action
- [ ] test: The test action
- [ ] profile: The profile action
- [ ] analyze: The analyze action
- [ ] archive: The archive action
- [ ] management: management metadata
Build  Copy Section
- [x] targets: [String:String] or [String:[String]] - A map of target names to build and which build types they should be enabled for. The build types can be all, none, or an array of the following types:
	- run or running
	- test or testing
	- profile or profiling
	- analyze or analyzing
	- archive or archiving
- [ ] parallelizeBuild: Bool - Whether or not your targets should be built in parallel. By default this is true if not set.
  - true: Build targets in parallel
  - false: Build targets serially
- [ ] buildImplicitDependencies: Bool - Flag to determine if Xcode should build implicit dependencies of this scheme. By default this is true if not set.
  - true: Discover implicit dependencies of this scheme
  - false: Only build explicit dependencies of this scheme
- [ ] runPostActionsOnFailure: Bool - Flag to determine if Xcode should run post scripts despite failure build. By default this is false if not set.
- true: Run post scripts even if build is failed
- false: Only run post scripts if build success

Common Build Action options  Copy Section
The different actions share some properties:
- [ ] config: String - All build actions can be set to use a certain config. If a config, or the build action itself, is not defined the first configuration found of a certain type will be used, depending on the type:
	- debug: run, test, analyze
	- release: profile, archive
- [ ] commandLineArguments: [String:Bool] - run, test and profile actions have a map of command line arguments to whether they are enabled
- [ ] preActions: [Execution Action] - Scripts that are run before the action
- [ ] postActions: [Execution Action] - Scripts that are run after the action
- [ ] environmentVariables: [Environment Variable] or [String:String] - run, test and profile actions can define the environment variables. When passing a dictionary, every key-value entry maps to a corresponding variable that is enabled.
- [ ] enableGPUFrameCaptureMode: GPUFrameCaptureMode - Property value set for GPU Frame Capture. Possible values are autoEnabled, metal, openGL, disabled. Default is autoEnabled.
- [ ] enableGPUValidationMode: Bool - Property value set for Metal API Validation. This defaults to true.
- [ ] disableMainThreadChecker: Bool - run and test actions can define a boolean that indicates that this scheme should disable the Main Thread Checker. This defaults to false
- [ ] stopOnEveryMainThreadCheckerIssue: Bool - a boolean that indicates if this scheme should stop at every Main Thread Checker issue. This defaults to false
- [ ] disableThreadPerformanceChecker: Bool - run action can define a boolean that indicates that this scheme should disable the Thread Performance Checker. This defaults to false
- [ ] language: String - run and test actions can define a language that is used for Application Language
- [ ] region: String - run and test actions can define a language that is used for Application Region
- [ ] debugEnabled: Bool - run and test actions can define a whether debugger should be used. This defaults to true.
- [ ] simulateLocation: Simulate Location - run action can define a simulated location
- [ ] askForAppToLaunch: Bool - run and profile actions can define the executable set to ask to launch. This defaults to false.
- [ ] launchAutomaticallySubstyle: String - run action can define the launch automatically substyle ('2' for extensions).
- [ ] storeKitConfiguration: String - run action can specify a storekit configuration. See Options.
- [ ] macroExpansion: String - run and test actions can define the macro expansion from other target. This defaults to nil.
Execution Action  Copy Section
Scheme run scripts added via preActions or postActions. They run before or after a build action, respectively, and in the order defined. Each execution action can contain:
- [x] script: String - an inline shell script
- [ ] name: String - name of a script. Defaults to Run Script
- [ ] settingsTarget: String - name of a build or test target whose settings will be available as environment variables.
A multiline script can be written using the various YAML multiline methods, for example with |. See Build Script.
Run Action  Copy Section

- [ ] executable: String - the name of the target to launch as an executable. Defaults to the first runnable build target in the scheme, or the first build target if a runnable build target is not found
- [ ] customLLDBInit: String - the absolute path to the custom .lldbinit file
- [ ] customWorkingDirectory: String - a path to use as the working directory when launching the executable.
Test Action  Copy Section
- [ ] gatherCoverageData: Bool - a boolean that indicates if this scheme should gather coverage data. This defaults to false
- [ ] coverageTargets: [Testable Target Reference] - a list of targets to gather code coverage. Each entry can either be a simple string, a string using Project Reference or Testable Target Reference
- [ ] targets: [Test Target] - a list of targets to test. Each entry can either be a simple string, or a Test Target
- [ ] customLLDBInit: String - the absolute path to the custom .lldbinit file
- [ ] captureScreenshotsAutomatically: Bool - indicates whether screenshots should be captured automatically while UI Testing. This defaults to true.
- [ ] deleteScreenshotsWhenEachTestSucceeds: Bool - whether successful UI tests should cause automatically-captured screenshots to be deleted. If captureScreenshotsAutomatically is false, this value is ignored. This defaults to true.
- [ ] testPlans:  [Test Plan] - List of test plan locations that will be referenced in the scheme.
- [ ] preferredScreenCaptureFormat: String - automatic screen capture format to use while UI Testing. Possible values are screenshots, screenRecording. Default is screenRecording.
#### Test Target
A target can be one of a 2 types:
- name: String - The name of the target.
- target: Testable Target Reference - The information of the target. You can specify more detailed information than name:.
As syntax sugar, you can also specify Testable Target Reference without target.
#### Other Parameters
- [ ] parallelizable: Bool - Whether to run tests in parallel. Defaults to false
- [ ] randomExecutionOrder: Bool - Whether to run tests in a random order. Defaults to false
- [ ] location: String - GPX file or predefined value for simulating location. See Simulate Location for location examples.
- [ ] skipped: Bool - Whether to skip all of the test target tests. Defaults to false
- [ ] skippedTests: [String] - List of tests in the test target to skip. Defaults to empty
- [ ] selectedTests: [String] - List of tests in the test target to whitelist and select. Defaults to empty. This will override skippedTests if provided
#### Testable Target Reference
A Testable Target Reference can be one of 3 types:
- package: {local-swift-package-name}/{target-name}: Name of local swift package and its target.
- local: {target-name}:  Name of local target.
- project: {project-reference-name}/{target-name}:  Name of local swift package and its target.
Archive Action  Copy Section
- [ ] customArchiveName: String - the custom name to give to the archive
- [ ] revealArchiveInOrganizer: Bool - flag to determine whether the archive will be revealed in Xcode's Organizer after it's done building

Simulate Location  Copy Section

- [x] allow: Bool - enable location simulation 
- [ ] defaultLocation: String - set the default location, possible values:
	- London, England
	- Johannesburg, South Africa
	- Moscow, Russia
	- Mumbai, India
	- Tokyo, Japan
	- Sydney, Australia
	- Hong Kong, China
	- Honolulu, HI, USA
	- San Francisco, CA, USA
	- Mexico City, Mexico
	- New York, NY, USA
	- Rio de Janeiro, Brazil
	- <relative-path-to-gpx-file> (e.g. ./location.gpx)   
	 Setting the defaultLocation to a custom gpx file, you also need to add that file to fileGroups for Xcode be able to use it:

Note that the path the gpx file will be prefixed according to the schemePathPrefix option in order to support both .xcodeproj and .xcworkspace setups. See Options.
Scheme Management  Copy Section

- [ ] shared: Bool - indicates whether the scheme is shared
- [ ] orderHint: Int - used by Xcode to sort the schemes
- [ ] isShown: Bool - indicates whether the sheme is shown in the scheme list
Environment Variable  Copy Section
- [x] variable: String - variable's name.
- [x] value: String - variable's value.
- [ ] isEnabled: Bool - indicates whether the environment variable is enabled. This defaults to true.

Test Plan  Copy Section

For now test plans are not generated by XcodeGen and must be created in Xcode and checked in, and then referenced by path. If the test targets are added, removed or renamed, the test plans may need to be updated in Xcode.
- [x] path: String - path that provides the xctestplan location.
- [ ] defaultPlan: Bool - a bool that defines if given plan is the default one. Defaults to false. If no default is set on any test plan, the first plan is set as the default.

Scheme Template  Copy Chapter
This is a template that can be referenced from a normal scheme using the templates property. The properties of this template are the same as a Scheme. This functions identically in practice to Target Template.
Any instances of ${scheme_name} within each template will be replaced by the final scheme name which references the template.
Any attributes defined within a scheme's templateAttributes will be used to replace any attribute references in the template using the syntax ${attribute_name}.

The result will be a scheme that builds MyModule when you request a build, and will test against MyModuleTests when you request to run tests. This is particularly useful when you work in a very modular application and each module has a similar structure.
Swift Package  Copy Chapter

Swift packages are defined at a project level, and then linked to individual targets via a Dependency.
Remote Package  Copy Section
- [x] url: URL - the url to the package
- [x] version: String - the version of the package to use. It can take a few forms:
  - majorVersion: 1.2.0 or from: 1.2.0
  - minorVersion: 1.2.1
  - exactVersion: 1.2.1 or version: 1.2.1
  - minVersion: 1.0.0, maxVersion: 1.2.9
  - branch: master
  - revision: xxxxxx
- [ ] github : String- this is an optional helper you can use for github repos. Instead of specifying the full url in url you can just specify the github org and repo
- [ ] traits: [String] - Optional Swift package traits to enable for this package reference. Trait names are written to the Xcode project in the specified order.
  
Local Package  Copy Section
- [x] path: String - the path to the package in local. The path must be directory with a Package.swift.
- [ ] group : String- Optional path that specifies the location where the package will live in your xcode project. Use "" to specify the project root.
- [ ] excludeFromProject : String- Optional flag to exclude the package from the generated project (useful if the package is already added via xcworkspace and the project is not intended for standalone use), defaults to false
- [ ] traits: [String] - Optional Swift package traits to enable for this package reference. Use the top-level packages mapping because the legacy localPackages syntax cannot specify traits.

Project Reference  Copy Chapter
Project References are defined at a project level, and then you can use the project name to refer its target via a Scheme
- [x] path: String - The path to the xcodeproj file to reference.

---
Docs/Usage  Copy Section
- Configuring build settings
    - Setting Presets
    - Settings
    - Setting Groups
    - xcconfig files
- Dependencies
    - CocoaPods
    - Carthage
    - Swift Package
    - SDK
    - Framework
Configuring build settings

There are various ways of configuring build settings
Xcode resolves a certain build setting for a configuration and target by looking up the different levels until it finds a value. This can be seen in Xcode when the Levels option is on in the Build Settings tab. The different levels of build settings are:
- target
- target xcconfig file
- project
- project xcconfig file
- sdk defaults
XcodeGen will apply settings to a target or project level by merging different methods
- Setting Presets
- Setting Groups
- Settings base
- Settings for a specific config
The values from xcconfig files will then sit a level above this. Note that as a convenience, any settings in an xcconfig file will also overwrite any settings from Setting Presets
>Note that when defining build settings you need to know the write name and value. In Xcode build settings are shown by default with a nicely formatted title and value. To be able to see what the actual build setting names and values are make sure you're in a Build Settings tab and go Editor -> Show Setting Titles and also Editor -> Show Definitions. This will then give you the actual names and values that XcodeGen expects.
Setting Presets  Copy Section

XcodeGen applies default settings to your project and targets similar to how Xcode creates them when you create a new project or target.
Debug and Release settings will be applied to your project. Targets will also get specific settings depending on the platform and product type.
>You can change or disable how these setting presets are applied via the options.settingPresets which you can find more about in Options
Settings  Copy Section

The project and each target have a settings object that you can define. This can be a simple map of build settings or can provide build settings per config via configs or base. See Settings for more details.

Setting Groups  Copy Section

Each settings can also reference one or more setting groups which let you reuse groups of build settings across targets or configurations. See Setting Groups for more details. Note that each setting group is also a full Settings object, so you can reference other groups or define settings by config.

xcconfig files  Copy Section

The project and each target have a configFiles object that lets you reference .xcconfig files per configuration.
>This is good guide to xcconfig files https://pewpewthespells.com/blog/xcconfig_guide

xcodebuild environment variables  Copy Section

You can also always override any build settings on CI when building by passing specific build settings to xcodebuild like so:

Dependencies
Each target can declare one or more dependencies. See Dependency in the ProjectSpec for more info about all the properties
CocoaPods  Copy Section

Use your Podfile as normal. The pods themselves don't need to be referenced in the project spec. After you generate your project simply run pod install which will integrate with your project and create a workspace.
Carthage  Copy Section

XcodeGen makes integrating Carthage dependencies super easy!
You simply reference them in each target that requires them and XcodeGen does the rest by automatically linking and embedding the carthage frameworks where necessary.

Some Carthage dependencies actually vend multiple frameworks. For example github "ReactiveCocoa/ReactiveCocoa" ~> 8.0 vends 2 frameworks ReactiveCocoa and ReactiveMapKit.
By default these all have to be listed if you want to link and use them:

XcodeGen can look these up for you automatically! This can be enabled with a global options.findCarthageFrameworks or can be overridden for each Carthage dependency. Note that if this is enabled, the Carthage dependencies need to have already been built before XcodeGen is run. This is because XcodeGen loads .version files that Carthage writes in the Carthage/Build directory which lists the all the frameworks. The name you use must also be the name of the .version file Carthage writes to Carthage/Build. Be aware that in some cases this name can differ from the name of the repo in the Cartfile and even the framework name. If the .version file is not found or fails parsing, XcodeGen will fallback to the regular Framework lookup in the relevant Carthage directory.

XcodeGen automatically creates the build phase that Carthage requires which lists all the files and runs carthage copy-frameworks. You can change the invocation of carthage to something different, for example if you are running it with Mint. This is then prepended to  copy frameworks

By default XcodeGen looks for carthage frameworks in Carthage/Build. You can change this with the carthageBuildPath option

Swift Package  Copy Section

Swift Packages can be integrated by defining them at the project level and then referencing them in targets

If you want to check in the Package.resolved file so that everyone is on the same versions, you need to check in ProjectName.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved
Note that Swift Packages don't work in projects with configurations other than Debug and Release. That limitation is tracked here bugs.swift.org/browse/SR-10927
Specified local packages get put into a Packages group in the root of the project by default. This can be changed with options.localPackagesGroup.
SDK  Copy Section

System frameworks and libs can be linked by using the sdk dependency type. You can either specify frameworks or libs by using a .framework, .tbd or dylib filename, respectively

Framework  Copy Section

Individual frameworks can also be linked by specifying a path to them

Build Tool Plug-ins

XCodeGen supports working with Swift Package Plug-ins.
To use plugins, you need to specify in your target which plugin you want to connect, and don't forget to connect the package to target.

---
CHANGELOG  Copy Section
Change Log
2.46.0  Copy Chapter
Added  Copy Section

- Added support for Swift package traits on remote and local package references, so generated projects preserve the configured trait selections #1629 @philprime
Changed  Copy Section

- Targets in the generated project now follow the declaration order from the source spec (Xcode sidebar, xcodebuild -list output). Previously they were always sorted alphabetically. Applies to both YAML and JSON specs. Declaration order is now also preserved for targets whose platform/name come from a target template and for targets whose key is a ${VARIABLE}. #1619 @mirkokg
Internal  Copy Section

- Update to XcodeProj 9.14.0 #1629 @philprime
2.45.4  Copy Chapter
Fixed  Copy Section

- Fix makePathRelative using wrong base path when projectDirectory differs #1608 @yonaskolb
- Fix synced folder configFiles creating duplicate groups #1607 @AlexNsbmr
- Fix synced folder root group duplication for paths referenced by multiple targets #1607 @AlexNsbmr
- Fix synced folder directory-level membershipExceptions not working #1607 @AlexNsbmr
2.45.3  Copy Chapter
Fixed  Copy Section

- Fix folder source PBXFileReference path regression with createIntermediateGroups #1605 @yonaskolb
- Fix synced folders: includes silently ignored + no deduplication across targets #1604 @4brunu
2.45.2  Copy Chapter
Fixed  Copy Section

- Validate empty source paths to prevent project root inclusion #1601 @yonaskolb
- Fix missing productRefGroup in generated projects #1591 @ruslic19
2.45.1  Copy Chapter
Added  Copy Section

- Added built in .icon folder support for IconComposer #1600 @yonaskolb
2.45.0  Copy Chapter
Added  Copy Section

- Added ability to specify project format version via projectFormat option #1566 @anivaros
- Added explicitFolders property to TargetSource that is passed through to PBXFileSystemSynchronizedRootGroup, to turn entire subfolders into Resources #1596 @macguru
- Allow synced folders to be sorted using groupOrdering #1596 @macguru
- Added excludes support for syncedFolder sources with glob pattern matching #1587 @mirkokg
Fixed  Copy Section

- Fixed synced folders ignoring createIntermediateGroups=YES and always being created at the root level #1596 @macguru
- Fix membership exceptions not working for nested synced folders with intermediate groups enabled #1596 @macguru
- Fix supportedDestinations presets being injected when settingPresets is none #1599 @macguru
- Automatically exclude Info.plist from synced folder membership when it's within the synced folder #1587 @mirkokg
- Add empty copy resources build phase for synced folders so resources are copied correctly #1587 @mirkokg
Internal  Copy Section

- Update to XcodeProj 9.10.1 #1597 @yonaskolb
- Fix CI: add explicit xcodebuild destinations and update Xcode matrix #1594 @yonaskolb
- Update ArtifactBundleGen to 0.0.8 #1570 @georgenavarro
2.44.1  Copy Chapter
Fixed  Copy Section

- Set the correct object version of 77 for Xcode 16 projects @jakobfelsatdm #1563
- Support major.minor SPM package versions which would otherwise fail to decode to a string in yaml specs #1546 @RomanPodymov
- Fix regression for parallelizable in scheme. It now resolves to "Enabled" and not "Swift Testing Only" #1565 @CraigSiemens
2.44.0  Copy Chapter
Added  Copy Section

- Basic support for Xcode 16's synchronized folders #1541 @yonaskolb
  - TargetSource.type can now be syncedFolder
  - Options.defaultSourceDirectoryType can be set to syncedFolder for the default type in all sources in the project (defaults to group)
  - Benefits include faster generation and no cache invalidation or need to regenerate when files are added or removed from these folders
  - Note that not all TargetSource options like excludes are supported, just a simple path. Please test and see what is missing in your projects
- Added sanitizer options to run and test actions in Scheme #1550 @hi-kumar
Fixed  Copy Section

- Added validation to ensure that all values in settings.configs are mappings. Previously, passing non-mapping values did not raise an error, making it difficult to detect misconfigurations. Now, SpecParsingError.invalidConfigsMappingFormat is thrown if misused. #1547 @Ryu0118
- Use USER instead of LOGNAME for XCUserData #1559 @KostyaSha
2.43.0  Copy Chapter
Added  Copy Section
- Added excludeFromProject from local packages #1512 @maximkrouk
- Added support for preferredScreenCaptureFormat in schemes #1450 @vakhidbetrakhmadov
Changes  Copy Section
- .appex files are now copied to plugins directory by default #1531 @iljaiwas
- The preGenCommand is now run before validation and caching #1500 #1519 @simonbs @dalemyers
- Improve performance of spec validation #1522 @zewuchen
- The enableGPUValidationMode enum is deprecated and is now a boolean #1515 @marcosgriselli @yonaskolb
Fixed  Copy Section
- Breaking: fileGroups are now relative paths when in included files, like other paths #1534 @shnhrrsn
- Breaking: Local package paths are now relative paths when in included files, like other paths #1498 @juri
- Optional groups are no longer skipped when missing and generating projects from a different directory #1529 @SSheldon
Internal  Copy Section
- Fix Swift 6.0 warnings #1513 @marcosgriselli
- Update package swift tools to 5.9 #1489 @0111b
- Add Xcode 16 to CI #1439 @giginet
- Fix test project building on CI #1537 @yonaskolb
- Skip failing tests on Linux #1517 @marcosgriselli
- XcodeProj updated to 8.24.3 #1515 @marcosgriselli @yonaskolb
2.42.0  Copy Chapter
Added  Copy Section
- Better support for local Swift packages in Xcode 15 #1465 @kinnarr
- Added macroExpansion to test actions in schemes #1468 @erneestoc
Changed  Copy Section
- Better default macroExpansion target in schemes #1471 @erneestoc
Removed  Copy Section
- Removed xcodegen dump --type graphviz as graphviz no longer builds in Swift 6 and is no longer maintained. If anyone uses this feature and wishes to keep it, please submit a PR providing a suitable alternative. #1485 @giginet
2.41.0  Copy Chapter
Added  Copy Section
- Added xcodegen cache command that writes the cache. Useful for post-commit git hook integration #1476 @yonaskolb
Changed  Copy Section
- Include folders in file sorting #1466 @jflan-dd
Fixed  Copy Section
- Fixed supportedDestinations validation when it contains watchOS for multiplatform apps. #1470 @tatsuky
2.40.1  Copy Chapter
Fixed  Copy Section
- Reverted .xcprivacy handling. They will now again be treated as resources by default @yonaskolb
2.40.0  Copy Chapter
Added  Copy Section
- Added support for local Swift packages at the project root by specifying a "" group #1413 @hiltonc
- Added a custom shell to a scheme's pre and post actions #1430 @balazs-vimn
Changed  Copy Section
- .xcprivacy files are now not added to any build phases by default #1464 @yonaskolb
2.39.1  Copy Chapter
Added  Copy Section
- Proper defaults for .cp and .cxx files #1447 @eschwieb
Fixed  Copy Section
- Fixed bundle access crash #1448 @freddi-kit
- Pinned XcodeProj version to fix breaking changes when XcodeGen is used as a dependency #1449 @yonaskolb
2.39.0  Copy Chapter
Added  Copy Section
- Support Artifact Bundle #1388 @freddi-kit
- Added support for .xcstrings String Catalogs #1421 @nicolasbosi95
- Added default LD_RUNPATH_SEARCH_PATHS for visionOS #1444 @Dahlgren
- Added watchOS as a supported cross platform destination #1438 @tatsuky
Fixed  Copy Section
- Fixed custom local package groups not being created #1416 @JaapManenschijn
- Fixed spec validation error type #1439 @Lutzifer
- Create parent group for local package groups if it does not exist already #1417 @JaapManenschijn
Internal  Copy Section
- Updated Rainbow version #1424 @nysander
2.38.0  Copy Chapter
Added  Copy Section
- Multi-destination targets #1336 @amatig
  - Added supportedDestinations to target
  - Added optional new platform value of auto when using supportedDestinations
  - Added destinationFilters for sources and dependencies
  - Added inferDestinationFiltersByPath, a convenience filter for sources
- .mlpackage files now default to being a source type #1398 @aaron-foreflight
- Added support for Build Tool Plug-ins in AggregateTarget #1390 @BarredEwe
Fixed  Copy Section
- Fixed source file includes not working when no paths were found #1337 @shnhrrsn
- Supports specifying multiple package products #1395 @simonbs
2.37.0  Copy Chapter
Added  Copy Section
- Added support for adding Build Tool Plug-ins to targets #1374 @BarredEwe
2.36.1  Copy Chapter
Fixed  Copy Section
- Revert addition of ENABLE_MODULE_VERIFIER build setting for causing issues in tests and some setups #1387 @yonaskolb
2.36.0  Copy Chapter
Added  Copy Section
- Added scheme.enableGPUValidationMode #1294 @LouisLWang
- Added visionOS support #1379 @shiba1014
- Added ability to disable Thread performance checker in Schemes #1380 @piellarda
- Added support for RuntimeIssue breakpoints #1384 @yonaskolb
Changed  Copy Section
- The project object version has been updated for Xcode 14.3 #1368 @leonardorock
- Updated recommended settings for Xcode 14.3 #1385 @yonaskolb
- Dropped support for Xcode 12 and 13, due to XcodeProj update #1384 @yonaskolb
Fixed  Copy Section
- Fix external dependencies from being removed by Xcode #1354 @OdNairy
- Stop creating orphaned object references when reusing references to external dependencies #1377 @liamnichols
2.35.0  Copy Chapter
Added  Copy Section
- Added support for shared breakpoints #177 @alexruperez @myihsan
- Added support for putResourcesBeforeSourcesBuildPhase in a target #1351 @mat1th
Fixed  Copy Section
- Fix case where source paths may not be deduplicated correctly resulting in duplicate groups and/or a crash in running Xcodegen #1341 @dalemyers
2.34.0  Copy Chapter
Changed  Copy Section
- Added support for swiftcrossimport folders. #1317 @Iron-Ham
- Added support for Scheme Management #1142 @wendyliga, @teameh
Fixed  Copy Section
- Fix includes when the projectRoot is a relative path #1262 @CraigSiemens
- Renamed build phase Embed App Extensions to Embed Foundation Extensions to fix Xcode 14 warning #1310 @casperriboe
2.33.0  Copy Chapter
Added  Copy Section
- Added support for enableGPUFrameCaptureMode #1251 @bsudekum
- Config setting presets can now also be loaded from the main bundle when bundling XcodeGenKit #1135 @SofteqDG
- Added ability to generate multiple projects in one XcodeGen launch #1270 @skofgar
- Use memoization during recursive SpecFiles creation. This provides a drastic performance boost with lots of recursive includes #1275 @ma-oli
Fixed  Copy Section
- Fix scheme not being generated for aggregate targets #1250 @CraigSiemens
- Fix recursive include path when relativePath is not set #1275 @ma-oli
- Include projectRoot in include paths #1275 @ma-oli
Internal  Copy Section

- Updated to Yams 5.0.1 #1297 @s2mr
- Delete ignored try keyword #1298 @s2mr
2.32.0  Copy Chapter
Added  Copy Section
- Add support for mlmodelc files #1236 @antonsergeev88
- Add enable option for include #1242 @freddi-kit
Fixed  Copy Section
- Fix checking environment variable in include #1242 @freddi-kit
- Fix profile action for frameworks in Xcode 14 #1245 @SSheldon
2.31.0  Copy Chapter
Added  Copy Section
- Added a new CopyFilesBuildPhase, "Embed ExtensionKit Extensions" #1230 @mtj0928
- Added duplicate dependencies validation #1234 @aleksproger
2.30.0  Copy Chapter
Added  Copy Section
- Added support for new target type extensionkit-extension in Xcode 14 #1228 @aleksproger
Changed  Copy Section
- Speed up generating build settings for large projects #1221 @jpsim
Fixed  Copy Section
- Fix XcodeGen building as library after breaking XcodeProj update 8.8.0 #1228 @aleksproger
2.29.0  Copy Chapter
Some support for Xcode Test Plans has been added. For now test plans are not generated by XcodeGen and must be created in Xcode and checked in, and then referenced by path. If the test targets are added, removed or renamed, the test plans may need to be updated in Xcode
#### Added
- Schemes and Target Schemes can now reference existing Test Plans under {scheme}.test.testPlans and {target}.scheme.testPlans, respectively. #716 @yonaskolb @omares
#### Fixed
- Fixed an issue where DocC was not added to source file list #1202 @hiragram
#### Changed
- Updated XcodeProj to 8.7.1 #1213 @yonaskolb
2.28.0  Copy Chapter
#### Added
- Support for specifying custom group locations for SPM packages. #1173 @John-Connolly
Fixed  Copy Section
- Fix Monterey macOS shell version, shell login flag for environments #1167 @bimawa
- Fixed crash caused by a simultaneous write during a glob processing #1177 @tr1ckyf0x
Changed  Copy Section
- Run target source pattern matching in parallel #1197 @alvarhansen
2.27.0  Copy Chapter
#### Added
- Support test target for local Swift Package #1074 @freddi-kit
- Added coverageTargets for target test schemes. This enables to gather code coverage for specific targets. #1189 @gabriellanata
- Fixed issue where .gyb files could not be added to source file list #1191 @hakkurishian
Fixed  Copy Section
- Fixed crash caused by a simultaneous write during a glob processing #1177 @tr1ckyf0x
- Skip generating empty compile sources build phases for watch apps #1185 @evandcoleman
2.26.0  Copy Chapter
Added  Copy Section
- Added the option to specify a location in a test target #1150 @KrisRJack
Changed  Copy Section
- Speed up source inclusion checking for big projects #1122 @PaulTaykalo
2.25.0  Copy Chapter
Added  Copy Section
- Allow specifying a copy setting for each dependency. #1038 @JakubBednar
Fixed  Copy Section
- Fix broken codesign option for bundle dependency #1104 @kateinoigakukun
- Ensure fileTypes are mapped to JSON value #1112 @namolnad
- Fix platform filter for package dependecies #1123 @raptorxcz
- Fix Xcode 13 build #1130 @raptorxcz @mthole
Changed  Copy Section
- Update XcodeProj to 8.2.0 #1125 @nnsnodnb
2.24.0  Copy Chapter
Added  Copy Section
- Added support for DocC Catalogs #1091 @brevansio
- Added support for "driver-extension" and "system-extension" product types #1092 @vgorloff
- Add support for conditionally linking dependencies for specific platforms #1087 @daltonclaybrook
- Add ability to specify UI testing screenshot behavior in test schemes #942 @daltonclaybrook
Changed  Copy Section
- Breaking: Rename the platform field on Dependency to platformFilter #1087 @daltonclaybrook
2.23.1  Copy Chapter
Changed  Copy Section
- Reverted "Change FRAMEWORK_SEARCH_PATH for xcframeworks (#1015)", introduced in 2.20.0. XCFrameworks need to be
  referenced directly in the project for Xcode's build system to extract the appropriate frameworks #1081 @elliottwilliams
2.23.0  Copy Chapter
#### Added
- Added ability to set custom platform for dependency #934 @raptorxcz
#### Fixed
- Added () to config variant trimming charater set to fix scheme config variant lookups for some configs like Debug (Development) that broke in 2.22.0 #1078 @DavidWoohyunLee
- Fixed Linux builds on Swift 5.4 #1083 @yonaskolb
2.22.0  Copy Chapter
#### Added
- Support runPostActionsOnFailure for running build post scripts on failing build #1075 @freddi-kit
#### Changed
- Xcode no longer alerts to project changes after regeneration, due to internal workspace not regenerating if identical #1072 @yonaskolb
#### Fixed
- Fixed no such module DOT error when package is used as a dependency #1067 @yanamura
- Fixed scheme config variant lookups for some configs like ProdDebug and Prod-Debug that broke in 2.21.0 #1070 @yonaskolb
2.21.0  Copy Chapter
#### Added
- Support weak link for Swift Package Dependency #1064 @freddi-kit
#### Changed
- Carthage frameworks are no longer embedded for "order-only" target dependencies. This avoid redundant embeds in situations where a target's sources _import_ a Carthage framework but do not have a binary dependency on it (like a test target which runs in a host app). #1041 @elliottwilliams
#### Fixed
- The Core target is renamed to avoid collisions with other packages. #1057 @elliottwilliams
- Lookup scheme config variants by whole words, fixing incorrect assignment in names that contain subtrings of each other (eg PreProd and Prod) #976 @stefanomondino
2.20.0  Copy Chapter
#### Added
- Allow specifying a github name like JohnSundell/Ink instead of a full url for Swift Packages #1029 @yonaskolb
- Added explicit LastUpgradeCheck and LastUpgradeVersion override support so it's possible to override these properties without using the project.xcodeVersion. 1013 @Andre113
- Added macroExpansion for run in schemes #1036 @freddi-kit
- Added askForAppToLaunch for profile in schemes #1035 @freddi-kit
- Added support for selectedTests in schemes Test configuration. #913 @ooodin
#### Fixed
- Fixed regression on .storekit configuration files' default build phase. #1026 @jcolicchio
- Fixed framework search paths when using .xcframeworks. #1015 @FranzBusch
- Fixed bug where schemes without a build target would crash instead of displaying an error #1040 @dalemyers
- Fixed files with names ending in Info.plist (such as GoogleServices-Info.plist) from being omitted from the Copy Resources build phase. Now, only the resolved info plist file for each specific target is omitted. #1027 @liamnichols
#### Internal
- Build universal binaries for release. XcodeGen now runs natively on Apple Silicon. #1024 @thii
2.19.0  Copy Chapter
#### Added
- Added support for building and running on Linux platforms. Tested for compatibility with Swift 5.3+ and Ubuntu 18.04. #988 @elliottwilliams
- Added useBaseInternationalization to Project Spec Options to opt out of Base Internationalization. #961 @liamnichols
- Added storeKitConfiguration to allow specifying StoreKit Configuration in Scheme and TargetScheme, supporting either xcodeproj or xcworkspace via schemePathPrefix option. #964 @jcolicchio
- Added more detailed error message with method arguments. #990 @bannzai
- Added basedOnDependencyAnalysis to Project Spec Build Script to be able to choose not to skip the script. #992 @myihsan
- Added BuildRule.runOncePerArchitecture to allow running build rules once per architecture. #950 @sascha
- Added discovered dependency file for a build script #1012 @polac24 @fggeraissate
#### Changed
- Breaking: Info.plists with custom prefixes are no longer added to the Copy Bundle Resources build phase #945 @anivaros
- Breaking: workingDirectory of included legacy targets is now made relative to including project #981 @jcolicchio
- Breaking: Make simulateLocation respect schemePathPrefix option. #973 @jcolicchio
#### Fixed
- Fixed error message output for minimumXcodeGenVersion. #967 @joshwalker
- Remove force-unwrapping causing crash for LegacyTargets #982 @jcolicchio
- Fixed a race condition in an internal JSON decoder, which would occasionally fail with an error like Parsing project spec failed: Error Domain=Unspecified error Code=0. #995 @elliottwilliams
- Fixed issue where frameworks with MACH_O_TYPE: staticlib were being incorrectly embedded. #1003 @mrabiciu
#### Internal
- Updated to Yams 4.0.0 #984 @swiftty
2.18.0  Copy Chapter
#### Added
- Add Scheme.Test.TestTarget.skipped to allow skipping of an entire test target. #916 @codeman9
- Added ability to set custom LLDBInit scripts for launch and test schemes #929 @polac24
- Adds App Clip support. #909 @brentleyjones @dflems
- Application extension schemes now default to launchAutomaticallySubstyle = 2 and the correct debugger and launcher identifiers #932 @brentleyjones
- Updated SettingsPresets to use new defaults from Xcode 12. #953 @liamnichols
- Enable Base Internationalization by default as per Xcode 12 behavior. #954 @liamnichols
#### Changed
- Change default project version to Xcode 12 #960 @yonaskolb
#### Internal
- Updates CI to run on Xcode 12. #936 @dflems @yonaskolb
#### Fixed
- Select the first runnable build target, if present. #957 @codeman9
- Allow SDK dependencies to be embedded. #922 @k-thorat
- Allow creating intermediary groups outside of the project directory. #892 @segiddins
- Fix appex's Runpath Search Paths under macOS target. #952 @rinsuki
- onlyCopyFilesOnInstall is extended for the Embed App Extensions build phase. #948 @RomanPodymov
2.17.0  Copy Chapter
#### Added
- Added options.fileTypes which lets you set cross project defaults for certain file extensions #914 @yonaskolb
- Added onlyCopyFilesOnInstall option to targets for the Embed Files build phase. #912 @jsorge
#### Fixed
- Treat all directories with known UTI as file wrapper. #896 @KhaosT
- Generated schemes for application extensions now contain wasCreatedForAppExtension = YES. #898 @muizidn
- Allow package dependencies to use link: false #920 @k-thorat
- Fixed issue computing relative paths.  #915 @andrewreach
#### Internal
- Updated to XcodeProj 7.13.0 #908 @brentleyjones
2.16.0  Copy Chapter
#### Added
- Improve speed of metadata parsing and dependency resolution. #803 @michaeleisel
- Improve support for iOS sticker packs and add support for launchAutomaticallySubstyle to run schemes. #824 @scelis
- Add --project-root option to generate command. #828 @ileitch
- Add an ability to set an order of groups with options.groupOrdering #613 @Beniamiiin
- Add the ability to output a dependency graph in graphviz format #852 @jeffctown
- Adds uncluttering the project manifest dumped to YAML from empty values #858 @paciej00
- Added ability to name the executable target when declaring schemes. #869 @elland
- Added ability to set executable to Ask to Launch. #871 @pinda
#### Fixed
- Fixed issue when linking and embedding static frameworks: they should be linked and NOT embed. #820 @acecilia
- Fixed issue when generating projects for paths with a dot in the folder for swift sources. #826 @asifmohd
- Prefix static library target filenames with 'lib' to match Xcode. #831 @ileitch
- Fixed duplicate addition of carthage static frameworks. #829 @funzin
- Fix handling of SWIFT_INSTALL_OBJC_HEADER when its value is YES/NO. #827 @ileitch
- Set preActions and postActions on the build action of a TargetScheme instead of the other actions. #823 @brentleyjones
- Prevent test targets from being set as a scheme's launch action #835 @brentleyjones
- Implicitly include bundles in the Copy Bundle Resources build phase. #838 @skirchmeier
- Fixed dumping a project manifest which contains an array of project references #840 @paciej00
- Generate correct PBXTargetDependency for external targets. #843 @ileitch
- Fix linking of multiple products from the same Swift Package #830 @toshi0383
- Don't deduplicate files in include with different path but same name. #849 @akkyie
- Don't link transitive static carthage libraries. #853 @akkyie
- Optimize simplifying paths for faster project generation. #857 @akkyie
- Fixed issue where wrapper folders may not include correctly in the generated project. #862 @KhaosT
- Compile xcmappingmodel files instead of copying bundle resources. #834 @jcolicchio
- Fixed issue where Complie Sources build phase is generated for resource bundles even when they have no files to compile #878 @nkukushkin
2.15.1  Copy Chapter
#### Fixed
- Fixed issue which caused watch app schemes to be generated incorrectly, preventing these apps from launching. #798 @daltonclaybrook
- Added build presets for the target type framework.static. #819 @acecilia
- Fixed XcodeProj resolution and updated to 7.10.0 #822 @soffes
2.15.0  Copy Chapter
#### Added
- Add support for local Swift Packages in packages using path. #808 @freddi-kit
- Add buildImplicitDependencies as an option on TargetScheme. #810 @evandcoleman
#### Fixed
- Fixed resolving path to local Swift Packages #796 @freddi-kit
- Added ability to stop on every main thread checker issue on Run schemes and TargetSchemes #799 @ionutivan
- Avoid copying ObjC interface header when SWIFT_INSTALL_OBJC_HEADER=false. #805 @kateinoigakukun
2.14.0  Copy Chapter
#### Added
- Add ability to embed and code sign Swift package dependencies with dynamic products. #788 @alexruperez
#### Fixed
- Revert "Add Base to known regions even if one doesn't exist" #791 @bryansum
- Set defaultConfigurationName for every target which is defined in a project. #787 @ken0nek
- Set TEST_TARGET_NAME only when a project has UITest bundle. #792 @ken0nek
- Set xcodeproj path in project.xcworkspace/contents.xcworkspacedata #793 @ken0nek
2.13.1  Copy Chapter
#### Fixed
- Validate scheme test action and test coverage target references before generating. #775 @liamnichols
- Fixed parsing prerelease identifiers in Swift package versions #779 @yonaskolb
- Fixed using legacy targets as dependencies #778 @yonaskolb
#### Internal
- Updated to XcodeProj 7.8.0 #777 @yonaskolb
- Use <https://github.com/mxcl/Version> #779 @yonaskolb
2.13.0  Copy Chapter
#### Added
- Support External Target References via subprojects. #701 @evandcoleman
#### Fixed
- Fixed compilation as library by locking down XcodeProj version #767 @yonaskolb
- Stabilized sorting of groups with duplicate names/paths. #671 @ChristopherRogers
- Moved Copy Bundle Resources to after Link with Libraries build phase #768 @yonaskolb
#### Internal
- Updated to XcodeProj 7.7.0 #767 @yonaskolb
2.12.0  Copy Chapter
#### Added
- Added pre and post command options. Useful for running pod install in combination with --use-cache #759 @yonaskolb
- Support for language and region settings on a target basis #728 @FranzBusch
- Added option to generate only Info.plist files with --only-plists #739 @namolnad
- Added the option to specify a simulateLocation in a scheme #722 @basvankuijck
- Support for On Demand Resources tags #753 @sipao
#### Fixed
- Fixed resolving a relative path for projectReference.path #740 @kateinoigakukun
- Don't add framework dependency's directory to FRAMEWORK_SEARCH_PATHS if it is implicit #744 @ikesyo @yutailang0119
- Fixed resolving relative path passed to XcodeProj #751 @PycKamil
- Prefer configurations named "Debug" or "Release" for default scheme build configurations #752 @john-flanagan
- Added an extra check for package versions. #755 @basvankuijck
#### Internal
- Update to SwiftCLI 6.0 and use the new property wrappers #749 @yonaskolb
2.11.0  Copy Chapter
#### Added
- Add Carthage static framework dependencies support. #688 @giginet
- Added xcodegen dump command #710 @yonaskolb
- Added --no-env option to disable environment variables expansion #704 @rcari
- Added custom group support for target sources #621 @sroebert @rcari
- Added new dependency type, bundle. This allows targets to copy bundles from other projects #616 @bsmith11
#### Fixed
- Improved variable expansion runtime #704 @rcari
- Fixed missing headers for static framework targets #705 @wag-miles
- Using more file types from XcodeProj for PBXFileReferences resulting in less project diffs #715 @yonaskolb
- Fixed localized *.intentdefinition not being added to build source phases #720 @giginet
- Fixed selectedLauncherIdentifier not being set Xcode.IDEFoundation.Launcher.PosixSpawn when debugEnabled: false is defined in test action #725 @ken0nek
- Fixed unnecessary dependencies related to SwiftPM #726 @tid-kijyun
#### Changed
- Deprecated $old_form variables in favor of ${new_form} variables #704 @rcari
- Updated XcodeProj to 7.4.0 #709 @yonaskolb
- Updated to Swift 5.1 #714 @yonaskolb
2.10.1  Copy Chapter
#### Fixed
- Add Base to knownRegions even if one doesn't exist #694 @bryansum
- Fixed missing onlyGenerateCoverageForSpecifiedTargets issue #700 @kateinoigakukun
- Fixed regression on dependencies link flag #703 @rcari
2.10.0  Copy Chapter
#### Added
- Support Target Reference to another project. #655 @kateinoigakukun
- Added coverageTargets for test target. This enables to gather code coverage for specific targets. #656 @kateinoigakukun
#### Fixed
- Add base localisation by default even if no base localised files were found. Fixes warning in Xcode 11 #685 @yonaskolb
- Don't generate CFBundleExecutable in default generated Info.plist for bundle target types #689 @FranzBusch
- Fixed resolving relative paths with custom project destination #681 @giginet
- Fixed resolving relative paths for Info.plist #683 @giginet
- Fixed macOS unit test target TEST_HOST #696 @mjarvis
#### Internal
- Restructure targets #698 @yonaskolb
2.9.0  Copy Chapter
#### Added
- Added Scheme Templates #672 @bclymer
#### Fixed
- Fixed macOS unit test setting preset #665 @yonaskolb
- Add rcproject files to sources build phase instead of resources #669 @Qusic
- Prefer default configuration names for generated schemes #673 @giginet
- Fixed some resource files being placed to "Recovered References" group #679 @nivanchikov
#### Internal
- Updated to SwiftCLI 5.3.2 #667 @giginet
- Fixed tests in case-sensitive file system #670 @Qusic
2.8.0  Copy Chapter
#### Added
- Added support for Swift Package dependencies #624 @yonaskolb
- Added includes to sources for a Target. This follows the same glob-style as excludes but functions as a way to only include files that match a specified pattern. Useful if you only want a certain file type, for example specifying /*.swift. #637 @bclymer
- Support dylib SDK. #650 @kateinoigakukun
- Added language and region options for run and test scheme #654 @kateinoigakukun
- Added debugEnabled option for run and test scheme #657 @kateinoigakukun
#### Fixed
- Expand template variable in Array of Any #651 @kateinoigakukun
- Significantly improve performance when running with a large number files. #658 @kateinoigakukun
- Removed some more diffs between the generated .pbxproj and when Xcode resaves it #663 @yonaskolb
#### Internal
- Removed needless Array initialization. #661 @RomanPodymov
- Updated to XcodeProj 7.1.0 #624 @yonaskolb
2.7.0  Copy Chapter
#### Added
- Added Bash 4 style recursive globbing (/*) in target sources excludes #636 @bclymer
- Added ability to disable main thread checker in Schemes #601 @wag-miles
#### Fixed
- Fixed included specs that were referenced multiple times from duplicating content #599 @haritowa
- Fixed .orig files being added to the project #627 @keith
#### Changed
- Allow linking of dependencies into static libraries when link is set to true #635 @kateinoigakukun
2.6.0  Copy Chapter
#### Added
- Added ability to skip tests #582 @kadarandras
- Added ability to set attributes on build files #583 @min
- Allow using environment variables in the form of ${SOME_VARIABLE}. This might be a breaking change when a target template attribute is also defined as an environment variable #594 @tomquist
- Added support for watchapp2-container and framework.static product types #604 @yonaskolb
#### Fixed
- Fixed .pch files being bundled as resources #597 @thii
- Fixed an issue that prevents watchOS Intents Extension from running correctly. #571 @KhaosT
#### Changed
- Updated the default compatibilityVersion project setting from Xcode 9.3 to Xcode 10.0 #581 @acecilia
- Updated to XcodeProj 7.0.0. Note that the length of generated UUIDs has changed #604 @yonaskolb
#### Internal
- Added ability to encode ProjectSpec #545 @ryohey
2.5.0  Copy Chapter
#### Added
- Added support for app-extension.intents-service target type #536 @yonaskolb
- Added support for custom root in sdk dependency #562 @raptorxcz
#### Changed
- Updated to xcodeproj 6.7.0 including its performance improvements #536 @yonaskolb
- Updated default generated settings for Xcode 10.2 #555 @yonaskolb
- Changed order of file generation so that plists are now generated before the project, so they will be included in the projects files #544 @tomquist
- Updated Yams to 2.0.0 @yonaskolb
#### Fixed
- Fixed groups from sources outside a project spec's directory from being flattened. #550 @sroebert
- Fixed optional file sources not being added to the project #557 @yonaskolb
- Fixed Carthage dependencies being incorrectly embedded in WatchKit app bundles instead of a WatchKit app extension #558 @KhaosT
2.4.0  Copy Chapter
#### Fixed
- Fixed installation when building in Swift 5 #549 @yonaskolb
#### Changed
- Updated to Swift 5 and dropped Swift 4.2 #549 @yonaskolb
2.3.0  Copy Chapter
#### Added
- Added ability to automatically find all the frameworks for Carthage dependencies via the global options.findCarthageFrameworks or dependency specific dependency.findFrameworks. See the Carthage usage docs for more info #506 @rpassis @yonaskolb
- Added support for nested target templates #534 @tomquist
- Added ability to define templateAttributes within a target to be able to parameterize templates. #533 @tomquist
- Added ability to set link to false in framework dependencies #532 @dimatosaurus
- Added missingConfigFiles to options.disabledValidations to optionally skip checking for the existence of config files.
- Added ability to define a per-platform deploymentTarget for Multi-Platform targets. #510 @ainopara
#### Changed
- DEPRECATION: Placeholders $target_name and $platform have been deprecated in favour of ${target_name} and ${platform}. Support for the old placeholders will be removed in a future version #533 @tomquist
#### Fixed
- Sources outside a project spec's directory will be correctly referenced as relative paths in the project file. #524
- Fixed error when optional directory source is missing #527 @yonaskolb
- Fixed excludes within included spec #535 @yonaskolb
- Fixed paths in target templates within included files not being relative #537 @yonaskolb
- Fix multi-platform target templates #541 @yonaskolb
- Fixed sources in an included target not being relative when the sources are mix of string and dictionaries #542 @yonaskolb
2.2.0  Copy Chapter
#### Added
- Added ability to generate empty directories via options.generateEmptyDirectories #480 @Beniamiiin
- Added support for the instrumentsPackage product type #482 @ksulliva
- Added support for inputFileLists and outputFileLists within project build scripts #500 @lukewakeford
- Added support for a $target_name replacement string within target templates #504 @yonaskolb
- Added createIntermediateGroups to individual Target Sources which overrides the top level option #505 @yonaskolb
#### Changed
- BREAKING: All the paths within include files are now relative to that file and not the root spec. This can be disabled with a relativePaths: false on the include. See the documentation for more details #489 @ellneal
- Updated the Xcode compatibility version from 3.2 to 9.3 #497 @yonaskolb
- Exact matches to config names in build settings won't partial apply to other configs #503 @yonaskolb
- UUIDs in the project are standard and don't contain any type prefixes anymore
#### Fixed
- Fixed --project argument not taking effect #487 @monowerker
- Fixed Sticker Packs from generating an empty Source file phase which caused in error in the new build system #492 @rpassis
- Fixed generated schemes for tool targets not setting the executable #496 @yonaskolb
- Fixed resolving Carthage dependencies for iOS app with watchOS target. 465 @raptorxcz
2.1.0  Copy Chapter
#### Added
- Added an experiment new caching feature. Pass --use-cache to opt in. This will read and write from a cache file to prevent unnecessarily generating the project. Give it a try as it may become the default in a future release #412 @yonaskolb
#### Changed
- Changed spelling of build phases to preBuildPhase and postBuildPhase. The older names are deprecated but still work 402 @brentleyjones
- Moved generation to a specific subcommand xcodegen generate. Simple xcodegen will continue to work for now #437 @yonaskolb
- If INFOPLIST_FILE has been set on a target, then an info path won't ovewrite it #443 @feischl97
#### Fixed
- Fixed XPC Service package type in generated Info.plist #435 @alvarhansen
- Fixed phase ordering for modulemap and static library header Copy File phases. 402 @brentleyjones
- Fixed intermittent errors when running multiple xcodegens concurrently #450 @bryansum
- Fixed --project argument not working #437 @yonaskolb
- Fixed unit tests not hooking up to host applications properly by default. They now generate a TEST_HOST and a TestTargetID #452 @yonaskolb
- Fixed static libraries not including external frameworks in their search paths #454 @brentleyjones
- Add .intentdefinition files to sources build phase instead of resources #442 @yonaskolb
- Add mlmodel files to sources build phase instead of resources #457 @dwb357
2.0.0  Copy Chapter
#### Added
- Added weak linking setting for dependencies #411 @alvarhansen
- Added info to targets for generating an Info.plist #415 @yonaskolb
- Added entitlements to targets for generating an .entitlement file #415 @yonaskolb
- Added sdk dependency type for linking system frameworks and libs #430 @yonaskolb
- Added parallelizable and randomExecutionOrder to Scheme test targets in an expanded form #434 @yonaskolb
- Validate incorrect config setting definitions #431 @yonaskolb
- Automatically set project SDKROOT if there is only a single platform within the project #433 @yonaskolb
#### Changed
- Performance improvements for large projects #388 @yonaskolb @kastiglione
- Upgraded to xcodeproj 6 #388 @yonaskolb
- Upgraded to Swift 4.2 #388 @yonaskolb
- Remove iOS codesigning sdk restriction in setting preset #414 @yonaskolb
- Changed default project version to Xcode 10.0 and default Swift version to 4.2 #423 @yonaskolb
- Added ability to not link Carthage frameworks #432 @yonaskolb
#### Fixed
- Fixed code signing issues #414 @yonaskolb
- Fixed TargetSource.headerVisibility not being set in initializer #419 @jerrymarino
- Fixed crash when using Xcode Legacy targets as dependencies #427 @dflems
1.11.2  Copy Chapter
If XcodeGen is compiled with Swift 4.2, then UUID's in the generated project will not be deterministic. This will be fixed in an upcoming release with an update to xcodeproj 6.0
#### Fixed
- Fixed release builds in Swift 4.2 #404 @pepibumur
- Fixed default settings for macOS unit-tests #387 @frankdilo
- Fixed Copy Headers phase ordering for Xcode 10 #401 @brentleyjones
- Fixed generated schemes on aggregate targets #394 @vgorloff
#### Changed
- Added en as default value for knownRegions #390 @Saik0s
- Update PathKit, Spectre, Yams and xcodeproj dependencies
1.11.1  Copy Chapter
#### Fixed
- Fixed FRAMEWORK_SEARCH_PATHS for framework dependency paths with spaces #382 @brentleyjones
- Fixed aggregate targets not being found with transitivelyLinkDependencies #383 @brentleyjones
1.11.0  Copy Chapter
#### Added
- Added showEnvVars to build scripts to disable printing the environment #351 @keith
- Added requiresObjCLinking to target #354 @brentleyjones
- Added targetTemplates #355 @yonaskolb
- Added aggregateTargets #353 @yonaskolb
- Added options.groupSortPosition #356 @yonaskolb
- Added ability to specify copyFiles build phase for sources #345 @brentleyjones
- Added ability to specify a minimumXcodeGenVersion #349 @brentleyjones
- Added customArchiveName and revealArchiveInOrganizer to archive  #367 @sxua
#### Fixed
- Sort files using localizedStandardCompare #341 @rohitpal440
- Use the latest xcdatamodel when sorted by version #341 @rohitpal440
- Fixed compiler flags being set on non source files in mixed build phase target sources #347 @brentleyjones
- Fixed options.xcodeVersion not being parsed #348 @brentleyjones
- Fixed non-application targets using carthage copy-frameworks #361 @brentleyjones
- Set xcdatamodel based on xccurrentversion if available #364 @rpassis
- XPC Services are now correctly copied #368 @brentley
- Fixed .metal files being added to resources #380 @vgorloff
#### Changed
- Improved linking for static.library targets #352 @brentleyjones
- Changed default group sorting to be after files #356 @yonaskolb
- Moved Frameworks and Products top level groups to bottom #356 @yonaskolb
- modulemap files are automatically copied to the products directory for static library targets #346 @brentleyjones
- Public header files are automatically copied to the products directory for static library targets #365 @brentleyjones
- Swift Objective-C Interface Header files are automatically copied to the products directory for static library targets #366 @brentleyjones
- FRAMEWORK_SEARCH_PATHS are adjusted for framework dependencies #373 @brentley
- library.static targets have SKIP_INSTALL set to YES #358 @brentley
- Copy files phases have descriptive names #360 @brentley
#### Internal
- Moved brew formula to homebrew core
- Added CONTRIBUTING.md
1.10.3  Copy Chapter
#### Fixed
- Fixed Mint installations finding SettingPresets #338 @yonaskolb
1.10.2  Copy Chapter
#### Changed
- Set transitivelyLinkDependencies to false by default
1.10.1  Copy Chapter
#### Fixed
- Fixed transitivelyLinkDependencies typo #332 @brentleyjones
- Fixed framework target dependencies not being code signed by default #332 @yonaskolb
#### Changed
- Code sign all dependencies by default except target executables #332 @yonaskolb
1.10.0  Copy Chapter
#### Added
- Added build rule support #306 @yonaskolb
- Added support for frameworks in sources #308 @keith
- Added ability to automatically embed transient dependencies. Controlled with transitivelyLinkDependencies #327 @brentleyjones
#### Changed
- Upgraded to Swift 4.1
- Improved Carthage dependency lookup performance with many targets #298 @keith
- By default don't CodeSignOnCopy target dependencies. This can still be controlled with Dependency.codeSign #324 @yonaskolb
#### Fixed
- Fixed PBXBuildFile and PBXFileReference being incorrectly generated for Legacy targets #296 @sascha
- Fixed required sources build phase not being generated if there are no sources #307 @yonaskolb
- Fixed install script in binary release #303 @alvarhansen
- Removed ENABLE_TESTABILITY from framework setting presets #299 @allu22
- Fixed homebrew installation #297 @vhbit
- cc files are now automatically recognized as source files #317 @maicki
- Fixed commandLineArguments not parsing when they had dots in them #323 @yonaskolb
- Fixed excluding directories that only have sub directories #326 @brentleyjones
- Made PBXContainerItemProxy ID more deterministic
- Fixed generated framework schemes from being executable #328 @brentleyjones
1.9.0  Copy Chapter
#### Added
- Scheme pre and post actions can now be added to target.scheme #280 @yonaskolb
- Individual files can now be added to fileGroups #293 @yonaskolb
#### Changed
- Updated to xcproj 4.3.0 for Xcode 9.3 updates
- Update default Xcode version to 9.3 including new settings #284 @LinusU
- Breaking for ProjectSpec library users Changed ProjectSpec to Project and ProjectSpec.Options to SpecOptions  #281 @jerrymarino
#### Fixed
- Fixed manual build phase of none not being applied to folders #288 @yonaskolb
- Quoted values now correctly get parsed as strings #282 @yonaskolb
- Fixed adding a root source folder when createIntermediateGroups is on #291 @yonaskolb
- Fixed Homebrew installations issues on some machines #289 @vhbit
- Fixed files that are added as root sources from having invalid parent groups outside the project directory #293 @yonaskolb
1.8.0  Copy Chapter
#### Added
- Added Project defaultConfig #269 @keith
- Added Target attributes #276 @yonaskolb
- Automatically set DevelopmentTeam and ProvisioningStyle within TargetAttributes if relevant build settings are defined #277 @yonaskolb
#### Fixed
- Fixed default LD_RUNPATH_SEARCH_PATHS for app extensions #272 @LinusU
#### Internal
- Make LegacyTarget init public #264 @jerrymarino
- Upgrade to _xcproj_ to 4.2.0, _Yams_ to 0.6.0 and _PathKit_ to 0.9.1 @yonaskolb
1.7.0  Copy Chapter
#### Added
- Added support for scheme environment variables #239 @turekj @toshi0383
- Added carthageExecutablePath option #244 @akkyie
- Added parallelizeBuild and buildImplicitDependencies to Schemes #241 @rahul-malik
 @yonaskolb
- Added support for Core Data xcdatamodeld files #249 @yonaskolb
- Projects are now generated atomically by writing to a temporary directory first #250 @yonaskolb
- Added script for adding precompiled binary to releases #246 @toshi0383
- Added optional headerVisibilty to target source. This still defaults to public #252 @yonaskolb
- Releases now include a pre-compiled binary and setting presets, including an install script
#### Fixed
- Fixed Mint installation from reading setting presets #248 @yonaskolb
- Fixed setting buildPhase on a folder source. This allows for a folder of header files #254 @toshi0383
- Carthage dependencies are not automatically embedded into test targets #256 @yonaskolb
- Carthage dependencies now respect the embed property #256 @yonaskolb
- iMessage extensions now have proper setting presets in regards to app icon and runtime search paths #255 @yonaskolb
- Excluded files are not added within .lproj directories #238 @toshi0383
1.6.0  Copy Chapter
#### Added
- Added scheme pre-actions and post-actions #231 @kastiglione
- Added options.disabledValidations including missingConfigs to disable project validation errors #220 @keith
- Generate UI Test Target Attributes #221 @anreitersimon
#### Fixed
- Filter out duplicate source files #217 @allu22
- Fixed how lastKnownFileType and explicitFileType were generated across platforms #115 @toshi0383
- Removed a few cases of project diffs when opening the project in Xcode @yonaskolb
- Fixed Swift not being embedded by default in watch apps @yonaskolb
#### Changed
- Change arrays to strings in setting presets #218 @allu22
- Updated to xcproj 4.0 #227
1.5.0  Copy Chapter
#### Added
- added support for gatherCoverageData flag in target schemes #170 @alexruperez
- added support for commandLineOptions in target schemes #172 @rahul-malik
- added Project spec as a SwiftPM library for reuse in other projects #164 @soffes
- added implicit option for framework dependencies #166 @sbarow
- added --quite option to CLI #167 @soffes
- can now print version with -v in addition to --version #174 @kastiglione
- added support for legacy targets #175 @bkase
- added support for indentation options #190 @bkase
- added source excludes #135 @peymankh @
- added options.xcodeVersion #197 @yonaskolb @peymankh
- add test targets to Scheme #195 @vhbit
- add option to make a source file optional incase it will be generated later #200 @vhbit
- finalize Scheme spec #201 @yonaskolb
- added buildPhase setting to target source for overriding the guessed build phase of files #206 @yonaskolb
- added deploymentTarget setting to project and target #205 @yonaskolb
#### Changed
- huge performance improvements when writing the project file due to changes in xcproj
- updated dependencies
- minor logging changes
- updated Project Spec documentation
- scan for Info.plist lazely #194 @kastiglione
- change setting presets so that icon settings only get applied to application targets #204 @yonaskolb
- changed scheme build targets format #203 @yonaskolb
- when specifying a --spec argument, the default for the --project path is now the directory containing the spec #211 @yonaskolb
#### Fixed
- fixed shell scripts escaping quotes twice #186 @allu22
- fixed createIntermediateGroups when using a relative spec path #184 @kastiglione
- fixed command line arguments for test and profile from being overridden #199 @vhbit
- fixed files deep within a hierarchy having the path for a name
- fixed source files from being duplicated if referenced with different casing #212 @yonaskolb
- fixed target product name not being written. Fixes integration with R.swift #213 @yonaskolb
1.4.0  Copy Chapter
#### Added
- added --version flag #112 @mironal
- added support for adding individual file sources #106 @bkase
- added source compiler flag support #121 @bkase
- added ProjectSpec.options.createIntermediateGroups #108 @bkase
- added better json loading support #127 @rahul-malik
- added source name for customizing names of source directories and file #146 @yonaskolb
- added folder reference source support via a new type property #151 @yonaskolb
- added ProjectSpec.options.developmentLanguage #155 @yonaskolb
#### Changed
- updated to xcproj 1.2.0 #113 @yonaskolb
- build settings from presets will be removed if they are provided in xcconfig files #77 @toshi0383
- all files and groups are sorted by type and then alphabetically #144 @yonaskolb
- target sources can now have an expanded form #119 @yonaskolb
- empty build phases are now not generated #149 @yonaskolb
- make UUIDs more deterministic #154 @yonaskolb
#### Fixed
- only add headers to frameworks and libraries #118 @ryohey
- fixed localized files with the same name #126 @ryohey
- fix intermediate sources #144 @yonaskolb
- fix cyclical target dependencies not working #147 @yonaskolb
- fix directory bundles not being added properly when referenced directly #148 @yonaskolb
- made mm, c and S file be parsed as source files #120 @bkase @enmiller
- fix the generation of localized variant groups if there is no Base.lproj #157 @ryohey
- all localizations found are added to a projects known regions #157 @ryohey
#### Internal
- refactoring
- more tests
- added release scripts
1.3.0  Copy Chapter
#### Added
- generate output files for Carthage copy-frameworks script #84 @mironal
- added options.settingPreset to choose which setting presets get applied #100 @yonaskolb
- added link option for target dependencies #109 @keith
#### Changed
- updated to xcproj 0.4.1 #85 @enmiller
- don't copy base settings if config type has been left out #100 @yonaskolb
- generate localised files under a single variant group #70 @ryohey
- don't apply common project settings to configs with no type #100 @yonaskolb
- config references in settings can now be partially matched and are case insensitive #111 @yonaskolb
- other small internal changes @yonaskolb
#### Fixed
- embed Carthage frameworks for macOS #82 @toshi0383
- fixed copying of watchOS app resources #96 @keith
- automatically ignore more file types for a target's sources (entitlements, gpx, apns) #94 @keith
- change make build to a PHONY task #98 @keith
- allow copying of resource files from dependant targets #95 @keith
- fixed library linking #93 @keith
- fixed duplicate carthage file references #107 @yonaskolb
- an error is now shown if you try and generate a target scheme and don't have debug and release builds @yonaskolb
1.2.4  Copy Chapter
#### Fixed
- setting presets only apply ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES: YES to applications
- don't add carthage dependency to copy-frameworks script if embed: false
- sort group children on APFS
#### Changed
- update to xcproj 0.3.0
1.2.3  Copy Chapter
#### Fixed
- Fixed wrong carthage directory name reference for macOS #74 @toshi0383
- Removed unnecessary carthage copy-frameworks for macOS app target #76 @toshi0383
- Added some missing default settings for framework targets. SKIP_INSTALL: YES fixes archiving
- Filter out nulls from setting presets if specifying an empty string
1.2.2  Copy Chapter
#### Added
- automatically set TEST_TARGET_NAME on UI test targets if one of the dependencies is an application target
#### Fixed
- set DYLIB_INSTALL_NAME_BASE to @rpath in framework target presets
- fixed tvOS launch screen setting. ASSETCATALOG_COMPILER_LAUNCHIMAGE_NAME is now LaunchImage not tvOS LaunchImage
1.2.0  Copy Chapter
#### Added
- include now supports a single string as well as a list
- add support setting xcconfig files on a project with configFiles #64
- add fileGroups to project spec for adding groups of files that aren't target source files #64
- better output (more info, emoji, colors)
- add options.bundleIdPrefix for autogenerating PRODUCT_BUNDLE_IDENTIFIER #67
- add :REPLACE syntax when merging include #68
- add mint installation support
#### Fixed
- fixed homebrew installation
- fixed target xcconfig files not working via configFiles #64
- look for INFOPLIST_FILE setting in project and xcconfig files before adding it automatically. It was just looking in target settings before #64
- exit with error on failure
1.1.0  Copy Chapter
#### Changed
- set project version to Xcode 9 - LastUpgradeVersion attribute to 0900
- set default Swift version to 4.0 - SWIFT_VERSION build setting to 4.0
1.0.1  Copy Section
Fixed  Copy Section
- fixed incorrect default build script shell path
- fixed install scripts
1.0.0  Copy Chapter
#### Added
- Swift 4 support #52
- Support for C and C++ files #48 by @antoniocasero
- Xcode 9 default settings
#### Fixed
- fixed empty string in YAML not being parsed properly #50 by @antoniocasero
#### Changed
- updated to xcodeproj 0.1.2 #56
- BREAKING: changed target definitions from list to map #54
0.6.1  Copy Chapter
#### Added
- Ability to set PBXProject attributes #45
#### Changed
- Don't bother linking target frameworks for target dependencies.
- Move code signing default settings from all iOS targets to iOS application targets, via Product + Platform setting preset files #46
0.6.0  Copy Chapter
#### Added
- Allow a project spec to include other project specs #44
#### Changed
- Changed default spec path to project.yml
- Changed default project directory to the current directory instead of the spec file's directory
0.5.1  Copy Chapter
#### Fixed
- Fix embedded framework dependencies
- Add CODE_SIGN_IDENTITY[sdk=iphoneos*] back to iOS targets
- Fix build scripts with "" generating invalid projects #43
0.5.0  Copy Chapter
#### Added
- Added multi platform targets #35
- Automatically generate platform specific FRAMEWORK_SEARCH_PATHS for Carthage dependencies #38
- Automatically find Info.plist and set INFOPLIST_FILE build setting if it doesn't exist on a target #40
- Add options for controlling embedding of dependencies #37
#### Fixed
- Fixed localized files not being added to a target's resources
#### Changed
- Renamed Setting Presets to Setting Groups
- Carthage group is now created under top level Frameworks group
0.4.0  Copy Chapter
##### Added
- Homebrew support #16 by @pepibumur
- Added runOnlyWhenInstalling to build scripts #32
- Added carthageBuildPath option #34
#### Fixed
- Fixed installations of XcodeGen not applying build setting presets for configs, products, and platforms, due to missing resources
#### Changed
- Upgraded to <https://github.com/swift-xcode/xcodeproj> 0.1.1 #33
0.3.0 - Extensions and Scheme Tests  Copy Chapter
#### Added
- Support for app extension dependencies, using the same target: MyExtension syntax #19
- Added test targets to generated target schemes via Target.scheme.testTargets #21
#### Changed
- Updated xcodeproj to 0.0.9
#### Fixed
- Fixed watch and messages apps not copying carthage dependencies
#### Breaking changes
- Changed Target.generatedSchemes to Target.scheme.configVariants
0.2.0 - Build scripts  Copy Chapter
#### Added
- Added Target build scripts with Target.prebuildScripts and Target.postbuildScripts #17
- Support for absolute paths in target sources, run script files, and config files
- Add validation for incorrect Target.configFiles
#### Fixed
- Fixed some project objects sometimes having duplicate ids
0.1.0  Copy Chapter
First official release
---
CONTRIBUTING  Copy Section
Contributing to XcodeGen
There are various ways to contribute to XcodeGen, and all are welcome and appreciated!
- Bug Reports
- Feature Requests
- Answering Questions
- Example Specs
- Documentation
- Code
Bug reports  Copy Chapter

Open issues about problems you may be encountering. When doing so please mention the version you're using xcodegen --version.
Feature Requests  Copy Chapter

If you have a good idea for a feature or enhancement open an issue. 
Answering Questions  Copy Chapter

Look through the open issues and answer any questions you can.
Example specs  Copy Chapter

Submit your open source xcodegen spec to the Examples page.
Documentation  Copy Chapter

Improve the documentation in the Docs directory.
Code  Copy Chapter

You can submit your own code. This can be bug fixes or new features. If you're not sure what to work on check out the open Issues
Getting started  Copy Section

Make sure you have at least Xcode 9.2 installed.
First clone the repo:

To make editing easier you can generate the Xcode project using Swift PM:

Targets  Copy Section

- ProjectSpec: Project spec definitions, loading, parsing and validation
- XcodeGen: XcodeGen CLI
- XcodeGenKit: All the logic for generation
- XcodeGenKitTests: Generation tests
Tests  Copy Section

Before submitting your PR run the tests to make sure they pass. This can be done either in Xcode or by running swift test.
As part of the tests there is a TestProject fixture that will be generated, and if the generated xcode project has any diff in it the test will fail. If the diff is a valid change, commit it as part of your changes.
Note that sometimes having the TestProject open in Xcode will generate it's own diffs, so make sure to have it closed when running the tests.
If your change contains any new features or logic changes please add a unit test of your own to cover it. If it's a new feature, see if it can be integrated into the TestProject by adding any required files and then editing the project spec.
Submitting your PR  Copy Section

Please give a small summary of what has changed. Also add any github issues links (Resolves #100).
Once your PR is created, please add a changelog entry to CHANGELOG.md along with the PR number.
---
README  Copy Section
<p align="center">
<a href="https://github.com/yonaskolb/XcodeGen">
<img src="Assets/Logo_animated.gif" alt="XcodeGen" />
</a>
</p>
<p align="center">
  <a href="https://github.com/yonaskolb/XcodeGen/releases">
    <img src="https://img.shields.io/github/release/yonaskolb/xcodegen.svg"/>
  </a>
  <a href="https://swiftpackageindex.com/yonaskolb/XcodeGen">
    <img src="https://img.shields.io/endpoint?url=https%3A%2F%2Fswiftpackageindex.com%2Fapi%2Fpackages%2Fyonaskolb%2FXcodeGen%2Fbadge%3Ftype%3Dplatforms" alt="Swift Package Manager Platforms" />
  </a>
  <a href="https://swiftpackageindex.com/yonaskolb/XcodeGen">
    <img src="https://img.shields.io/endpoint?url=https%3A%2F%2Fswiftpackageindex.com%2Fapi%2Fpackages%2Fyonaskolb%2FXcodeGen%2Fbadge%3Ftype%3Dswift-versions" alt="Swift Versions" />
  </a>
  <a href="https://github.com/yonaskolb/XcodeGen/blob/master/LICENSE">
    <img src="https://img.shields.io/github/license/yonaskolb/XcodeGen.svg"/>
  </a>
</p>
XcodeGen
XcodeGen is a command line tool written in Swift that generates your Xcode project using your folder structure and a project spec.
The project spec is a YAML or JSON file that defines your targets, configurations, schemes, custom build settings and many other options. All your source directories are automatically parsed and referenced appropriately while preserving your folder structure. Sensible defaults are used in many places, so you only need to customize what is needed. Very complex projects can also be defined using more advanced features.
- ✅ Generate projects on demand and remove your .xcodeproj from git, which means no more merge conflicts!
- ✅ Groups and files in Xcode are always synced to your directories on disk
- ✅ Easy configuration of projects which is human readable and git friendly
- ✅ Easily copy and paste files and directories without having to edit anything in Xcode
- ✅ Share build settings across multiple targets with build setting groups
- ✅ Automatically generate Schemes for different environments like test and production
- ✅ Easily create new projects with complicated setups on demand without messing around with Xcode
- ✅ Generate from anywhere including on CI
- ✅ Distribute your spec amongst multiple files for easy sharing and overriding
- ✅ Easily create multi-platform frameworks
- ✅ Integrate Carthage frameworks without any work
Given an example project spec:

A project would be created with 2 connected targets, with all the required configurations and build settings. See the Project Spec documentation for all the options you can specify, and Usage for more general documentation.
Installing  Copy Chapter
Make sure the latest stable (non-beta) version of Xcode is installed first.
Mint Mint')" title="Copy section prompt for LLMs"> Copy Section

Make  Copy Section

Homebrew  Copy Section

Swift Package Manager  Copy Section
Use as CLI

Use as dependency
Add the following to your Package.swift file's dependencies:

And then import wherever needed: import XcodeGenKit
Usage  Copy Chapter
Simply run:

This will look for a project spec in the current directory called project.yml and generate an Xcode project with the name defined in the spec.
Options:
- --spec: An optional path to a .yml or .json project spec. Defaults to project.yml. (It is also possible to link to multiple spec files by comma separating them. Note that all other flags will be the same.)
- --project: An optional path to a directory where the project will be generated. By default this is the directory the spec lives in.
- --quiet: Suppress informational and success messages.
- --use-cache: Used to prevent unnecessarily generating the project. If this is set, then a cache file will be written to when a project is generated. If xcodegen is later run but the spec and all the files it contains are the same, the project won't be generated.
- --cache-path: A custom path to use for your cache file. This defaults to ~/.xcodegen/cache/{PROJECT_SPEC_PATH_HASH}
There are other commands as well such as xcodegen dump which lets one output the resolved spec in many different formats, or write it to a file. Use xcodegen help to see more detailed usage information.
Editing  Copy Chapter