[Intermediate]: Add workflow to update dependabot PRs for changelog and assignee

[rbarker-dev]

🧩 Intermediate Contributors

This issue is intended for contributors who already have some familiarity with the
Hiero Python SDK codebase and contribution workflow.

You should feel comfortable:

• navigating existing source code and examples
• understanding SDK concepts without step-by-step guidance
• following the standard PR workflow without additional onboarding

If this is your very first contribution to the project, we recommend starting with a few
Good First Issues before working on this one.

🐞 Problem Description

Dependabot PRs are authored by the dependabot[bot]. When PRs are opened, they are not given an assignee and a changelog entry is not provided.

These items should be able to happen automagically using a github service account (SA) (@hiero-ledger/github-maintainers to help).

This PR should NOT modify any SDK functionality.

💡 Expected Solution

1. Add the @hiero-ledger/hiero-automation group to the hiero-sdk-python repository
2. Develop a workflow to update the changelog.md file and add the SA to the PR as an assignee.
3. Ensure the workflow can operate in dry-run mode (show what change would occur and who the assignee will be)
4. Test that when a PR is created by [test-user] that the changelog is updated to reflect the PR title
5. Ensure that when a dependabot PR is created, that the workflow picks up the change.

🧠 Implementation Notes

Add implementation notes here.

✅ Acceptance Criteria

To merge this issue, the pull request must:

• Fully address the problem described above
• Follow existing project conventions and patterns
• Include tests or example updates where appropriate
• Pass all CI checks
• Include a valid changelog entry
• be a DCO and GPG key signed as git commit -S -s -m "chore: my change" with a GPG key set up

📚 Additional Context or Resources

• SDK Developer Docs
• SDK Developer Training

[github-actions]

@coderabbitai plan

[github-actions]

Hello, this is CommunityCallBot.

This is a reminder that the Hiero Python SDK Community Call will begin in approximately 4 hours (14:00 UTC).

The call is an open forum where contributors and users can discuss topics, raise issues, and influence the direction of the Python SDK.

Details:

• Time: 14:00 UTC
• Join Link: Zoom Meeting

Disclaimer: This is an automated reminder. Please verify the schedule here for any changes.

[github-actions]

Hi @rbarker-dev 👋

This issue has been assigned but no pull request has been created yet.
Are you still planning on working on it?
If you are, please create a draft PR linked to this issue or comment /working to let us know.
If you’re no longer able to work on this issue, you can comment /unassign to release it.

From the Python SDK Team

[exploreriii]

Hi @rbarker-dev we have been able to merge a fair bit of our backlog, and can now invest more time on the mirror/security/dependabot issues, would you like us to take this ?

[github-actions]

Hi @rbarker-dev, this is InactivityBot 👋

You were assigned to this issue 21 days ago, and there is currently no open pull request linked to it.
To keep the backlog available for active contributors, I'm unassigning you for now.

If you're no longer interested, no action is needed.

Tip: You can comment /unassign on any issue to proactively step away before this bot kicks in.

If you'd like to continue working on this later, feel free to comment /assign on the issue to get re-assigned, and open a new PR when you're ready. 🚀

[exploreriii]

I can see how far I get with this

[exploreriii]

@coderabbitai plan

[coderabbitai]

Warning

A plan generation is already in progress. Please wait for it to complete before requesting a new plan.