Update to ACK runtime v0.56.0, code-generator v0.56.0

[ack-bot]

Update to ACK runtime v0.56.0, code-generator v0.56.0

---

• ACK code-generator v0.56.0 release notes
• ACK runtime v0.56.0 release notes

---

NOTE:
This PR increments the release version of service controller from v1.1.2 to v1.2.0

Once this PR is merged, release v1.2.0 will be automatically created for applicationautoscaling-controller

Please close this PR, if you do not want the new patch release for applicationautoscaling-controller

---

stdout for make build-controller:

building ack-generate ... ok.
==== building applicationautoscaling-controller ====
Copying common custom resource definitions into applicationautoscaling
Building Kubernetes API objects for applicationautoscaling
Generating deepcopy code for applicationautoscaling
Generating custom resource definitions for applicationautoscaling
Building service controller for applicationautoscaling
Running GO mod tidy
Generating RBAC manifests for applicationautoscaling
Running gofmt against generated code for applicationautoscaling
Updating additional GitHub repository maintenance files
==== building applicationautoscaling-controller release artifacts ====
Building release artifacts for applicationautoscaling-v1.2.0
Generating common custom resource definitions
Generating custom resource definitions for applicationautoscaling
Generating RBAC manifests for applicationautoscaling

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

To fix the issue, you must add an explicit permissions block to the workflow, either at the top level (root of the YAML) to apply to all jobs, or within the specific job definition to restrict that job's permissions. In this case, there is only a single job, so adding the permissions block at the root is preferrable for clarity, but placing it inside the job would also suffice. The minimal required permissions need to be chosen; if the workflow only needs the ability to read repository contents, contents: read is considered lowest privilege. If additional privileges are required by the called (reusable) workflow, you'd mirror those, but starting with contents: read is the secure default. Edit .github/workflows/postsubmit.yaml to include:

• Insert a permissions: block after the name: line, before on: (recommended location for root-level).
• The block should minimally be:

  permissions:
    contents: read
  

  This adheres to the principle of least privilege and satisfies CodeQL's requirements.

No imports, definitions, or extra methods are needed; YAML structure only.

[ack-prow]

@ack-bot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
applicationautoscaling-verify-code-gen	b9513ba	link	false	/test applicationautoscaling-verify-code-gen

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[a-hilaly]

/lgtm

[ack-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: a-hilaly, ack-bot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [a-hilaly]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment