# Managing and Updating Releases
Pandium simplifies the process of releasing a new version of an integration script and apply that code to existing tenants.
Releases are built through Pandium [Source Control](https://docs.pandium.com/integration-hub/setting-up-source-control). To view or manage these releases, start by navigating to the Integration Detail page.
### Building Releases From the Integration Page
Once an integration is created within Pandium, users can automatically populate integration scaffolding directly in the repository, including folder structure and language-specific files. This feature is beneficial for initiating development on an integration or when a change in repository information necessitates new scaffolding.
To start the process, simply click the ‘Setup Integration Repo’ button. This will then take you back to the Source Control page, where you can monitor the build starting in the Activity section.
If using this feature, Pandium will set up the following for you:
* A package file
* A main file to print out environment
* A lib file to parse Pandium specific environment
* A default PANDIUM.yaml
* Any additional files to get a minimally running script in that specific language
Alternatively, a manual build for a release can be started two different ways: clicking the ‘Build Release’ button on the main integration detail page, or via the Source Control tab in the ‘Settings’ resource.
In either case, Source Control is triggered to search for the defined path and repository information set in your integration configuration, subsequently constructing a new release based on those changes.
## Setting a Default Release
Within the integration configuration page, where repository settings are defined, locate the "Default Release" section. This default release becomes the version automatically provisioned to your customers upon installing the integration from your marketplace. It's crucial to have a default release selected for customers to install the integration. To select a release from the dropdown, you have to have built one or more release versions via[ source control](https://docs.pandium.com/platform-guides/engineering-guides/source-control).
There are three separate options for the default release behavior:
1. Static Default: Installed tenants maintain the currently set default integration release, remaining unchanged unless manually reset in the administrator platform.
2. Dynamic Default: Installed tenants are created using the current default integration release. If the integration default release changes, installed tenants will synchronize to match the new release on the next sync.
3. Latest: Tenants will always use the most recently-built release available for this integration.
{% hint style="info" %}
**Please Note:** When upgrading your release versions for your integrations, if there are any new configurations with default values, newly created tenants will reflect these values; all previously created tenants for your integration will not reflect these new default values. In order for these new changes to apply, you need to navigate to each respective tenant on your integration, pull up their tenant connection settings, and hit SAVE.
{% endhint %}
### Multi-yaml Support for Integrations
In the dynamic landscape of integrations, Pandium provides flexibility by enabling the creation and management of releases on an integration with multiple YAML files.
To use a different YAML file than the current setting, simply edit the repository path with the new YAML file path, then click ‘Build Release’ on the Integration detail page. Source Control will build a new release, ready to be applied to any tenant.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.pandium.com/integration-hub/updating-an-integrations-release.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.