Update to ACK runtime v0.54.1, code-generator v0.54.0

[ack-bot]

Update to ACK runtime v0.54.1, code-generator v0.54.0

---

• ACK code-generator v0.54.0 release notes
• ACK runtime v0.54.1 release notes

---

NOTE:
This PR increments the release version of service controller from v1.0.1 to v1.0.2

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

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

---

stdout for make build-controller:

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

---

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

[ack-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ack-bot
Once this PR has been reviewed and has the lgtm label, please assign michaelhtm for approval by writing /assign @michaelhtm in a comment. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

To fix the problem, add a permissions: block at the top level or at the job level of the workflow. Since the job simply delegates to a reusable workflow, we should apply the minimal required permissions here. Typically, contents: read is a secure starting point, unless more privileges are required (e.g., to write issues or pull requests--which, in this case, appears unnecessary). The best fix is to add the following under the workflow name: and before on::

permissions:
  contents: read

This change can be made at the top level of .github/workflows/postsubmit.yaml above the current on: block, ensuring that all jobs, including those that use reusable workflows, inherit only the minimum necessary permissions.

[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
bedrockagent-verify-code-gen	6a55d15	link	false	/test bedrockagent-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.

[knottnt]

/close

[ack-prow]

@knottnt: Closed this PR.

In response to this:

/close

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.