Release v0.50.1 (#5498)

Signed-off-by: Shinnosuke Sawada-Dazai <[email protected]>

RELEASE

@@ -1,6 +1,6 @@
 # Generated by `make release` command.
 # DO NOT EDIT.
-tag: v0.50.0
+tag: v0.50.1
 
 releaseNoteGenerator:
   showCommitter: false

docs/content/en/docs-v0.50.x/user-guide/configuration-reference.md

@@ -531,15 +531,12 @@ There are some restrictions in configuring a service definition file.
 - `deploymentController` is required and must be `EXTERNAL`.
 - `loadBalancers` is not supported. Use `targetGroups` in [ECSDeploymentInput](#ecsdeploymentinput) instead.
 - `platformFamily` is not supported.
-- `propagateTags` is always set as `SERVICE`.
 - `taskDefinition` is not supported. PipeCD uses the definition in `taskDefinitionFile` in [ECSDeploymentInput](#ecsdeploymentinput).
 
 ### Restrictions of Task Definition
 
 There are some restrictions in configuring a task definition file.
 
-- `placementConstraints` is not supported.
-- `proxyConfiguration` is not supported.
 - `tags` is not supported.
 
 ### ECSTargetGroupInput

docs/content/en/docs-v0.50.x/user-guide/managing-application/customizing-deployment/script-run.md

@@ -108,10 +108,12 @@ You can use the envrionment values related to the deployment.
 |SR_APPLICATION_NAME| The application name | example |
 |SR_TRIGGERED_AT| The timestamp when the deployment is triggered  | 1719571113 |
 |SR_TRIGGERED_COMMIT_HASH| The commit hash that triggered the deployment | 2bf969a3dad043aaf8ae6419943255e49377da0d |
+|SR_TRIGGERED_COMMANDER| The ID of user who triggered the deployment via UI. This is APIKey's ID if it was triggered via `pipectl sync`. This is empty if it was triggered by your piped. | userid |
 |SR_REPOSITORY_URL| The repository url configured in the piped config  | [email protected]:org/repo.git, https://github.com/org/repo |
 |SR_SUMMARY| The summary of the deployment | Sync with the specified pipeline because piped received a command from user via web console or pipectl|
 |SR_CONTEXT_RAW| The json encoded string of above values | {"deploymentID":"877625fc-196a-40f9-b6a9-99decd5494a0","applicationID":"8d7609e0-9ff6-4dc7-a5ac-39660768606a","applicationName":"example","triggeredAt":1719571113,"triggeredCommitHash":"2bf969a3dad043aaf8ae6419943255e49377da0d","repositoryURL":"[email protected]:org/repo.git","labels":{"env":"example","team":"product"}} |
 |SR_LABELS_XXX| The label attached to the deployment. The env name depends on the label name. For example, if a deployment has the labels `env:prd` and `team:server`, `SR_LABELS_ENV` and `SR_LABELS_TEAM` are registered.  | prd, server |
+|SR_IS_ROLLBACK| This is `true` if the deployment is rollbacking. Otherwise, this is `false`. | false |
 
 ### Use `SR_CONTEXT_RAW` with jq