🌱 Re-enable dependency report generation in main

[AnmolxSingh]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Dependency report generation was previously disabled as a temporary workaround due to Go toolchain incompatibilities.

Since the project now uses Go 1.24.x across build and tooling images, the original limitation no longer applies. This PR enables the dependency flag which was earlier disabled by #4825 and restores the default behavior of generating dependency reports as part of the release changelog process.

The release-notes tool and dependency report generation were validated locally using the current toolchain to ensure the workflow runs successfully.

Which issue this PR fixes:
Fixes #4826

Special notes for your reviewer:

Checklist:

• squashed commits
• includes documentation
• includes emoji in title
• adds unit tests
• adds or updates e2e tests

Release note:

NONE

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: AnmolxSingh / name: Anmol (38c5db2)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign andidog for approval. For more information see the Code Review Process.

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

Details

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

[k8s-ci-robot]

Welcome @AnmolxSingh!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-aws 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-provider-aws has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @AnmolxSingh. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[AnmolxSingh]

Hi @richardcase can you look into this pr? Thanks

[faiq]

/ok-to-test

[nrb]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Details

Git tree hash: ded7169c2df576a507bac4430ee10e1c851c7c5d