Merge pull request #5876 from mendix/kk-pc-relnotes

release notes and a minor api doc fix

Author: katarzyna-koltun-mx

content/en/docs/apidocs-mxsdk/apidocs/private-cloud-build-api.md

@@ -81,11 +81,11 @@ The following steps will create a deployment package, retrieve it, refresh its `
 4. Make the API call `POST /apps/{appId}/packages/build` using the deployment package JSON request to initiate the build of a new deployment package.
 5. Verify that the job is successful using the process described in [Managing Asynchronous Jobs](#async-jobs). 
 6. Call `GET /apps/{appId}/packages` to retrieve all the packages in the application. 
-7. Once the job that you launched in step 4 is successful, you will see a `packageId` in the response from Step 6. You can then call `GET /apps/{appId}/packages/{packageId}` to get the deployment package details.
-    The same `packageId` can the be used in step 12 from the [DeployAPI](/apidocs-mxsdk/apidocs/private-cloud-deploy-api/#restart) documentation.
+7. Once the job that you launched in step 4 is successful, you will see a `id` in the response from Step 6. You can then call `GET /apps/{appId}/packages/{id}` to get the deployment package details.
+    The same `id` can the be used in step 12 from the [DeployAPI](/apidocs-mxsdk/apidocs/private-cloud-deploy-api/#restart) documentation.
 8. Call `GET /apps/{appId}/packages` to retrieve all the deployment packages in the application. You should see the previously created deployment package in the list.
-9. If you want to download the deployment package locally, you can use the location URL present in the response from step 7. The URL has a lifetime of 15 minutes, so if more than 15 minutes have passed since the creation of the deployment package, you must request a new URL by calling `GET /apps/{appId}/packages/{packageId}?url=true`.
-10. Call `DELETE /apps/{appId}/packageId`, where you can get the package ID value from step 7.
+9. If you want to download the deployment package locally, you can use the location URL present in the response from step 7. The URL has a lifetime of 15 minutes, so if more than 15 minutes have passed since the creation of the deployment package, you must request a new URL by calling `GET /apps/{appId}/packages/{id}?url=true`.
+10. Call `DELETE /apps/{appId}/id`, where you can get the package ID value from step 7.
 11. Verify that the job is successful using the process described in [Managing Asynchronous Jobs](#async-jobs). 
 12. Call `GET /apps/{appId}/packages` to retrieve all the deployment packages in the application. The deployment package should be removed from the list.
 
@@ -101,8 +101,8 @@ Follow the steps below to upload a deployment package by using the API.
 2. Prepare the `multipart/form-data` request for your deployment package, as seen in the OpenAPI specification file. The `file` indicates the *.mda* file of the deployment package that you want to upload, and `fileName` represents the name with which the deployment package will be displayed in the Private Cloud Portal. If you do not provide the *.mda* extension to the *filename*, it is added automatically.
 3. Make the API call `POST /apps/{appId}/packages` using the request created in the previous step to upload the new deployment package.
 4. Verify that the job is successful using the process described in [Managing Asynchronous Jobs](#async-jobs).
-5. Once the previous job is successful, you will see a `packageId` in the response. You can then call `GET /apps/{appId}/packages/{packageId}` to get the deployment package details and verify the uploaded file.
-    You can use the same `packageId` when deploying an app through the [Mendix for Private Cloud Deploy API](/apidocs-mxsdk/apidocs/private-cloud-deploy-api/#api-deploy).
+5. Once the previous job is successful, you will see a `id` in the response. You can then call `GET /apps/{appId}/packages/{id}` to get the deployment package details and verify the uploaded file.
+    You can use the same `id` when deploying an app through the [Mendix for Private Cloud Deploy API](/apidocs-mxsdk/apidocs/private-cloud-deploy-api/#api-deploy).
 
 ## 4 API Reference
 

content/en/docs/releasenotes/deployment/_index.md

@@ -14,7 +14,7 @@ Follow the links in the table below to see the release notes you want:
 | Type of Deployment | Last Updated |
 | --- | --- |
 | [Mendix Cloud](/releasenotes/developer-portal/mendix-cloud/) | April 20th, 2023 |
-| [Mendix for Private Cloud](/releasenotes/developer-portal/mendix-for-private-cloud/) | April 13th, 2023 |
+| [Mendix for Private Cloud](/releasenotes/developer-portal/mendix-for-private-cloud/) | April 25th, 2023 |
 | [SAP Business Technology Platform (SAP BTP)](/releasenotes/developer-portal/sap-cloud-platform/) | November 17th, 2022 |
 | [Other Deployment Options](/releasenotes/developer-portal/on-premises/) | October 26th, 2020 |
 

content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md

@@ -13,6 +13,20 @@ For information on the current status of deployment to Mendix for Private Cloud
 
 ## 2023
 
+### April 25th, 2023
+
+#### Portal Improvements
+
+* We have improved the error message that displays when invalid values are provided in the custom core resources.
+* We have added a message in the namespace plan section that displays when a namespace is configured with a secret store.
+* We have improved the look and feel of the Private Cloud portal.
+* We now allow the upload of deployment packages larger than 500 MB (up until 1024 MB) from the user interface. (Ticket 180884)
+
+#### Deploy API
+
+* We have fixed an issue where the environment list could not be retrieved successfully when the app internal ID was shorter than 8 characters.
+* We have fixed an issue where upper-case letters in an email ID would prevent members invited to a cluster manager or namespace from retrieving the environments.
+
 ### April 13th, 2023
 
 #### Portal Enhancements