chore: release main

[baywet]

🤖 I have created a release beep boop

microsoft_kiota_abstractions: 0.0.2

0.0.2 (2025-01-09)

Bug Fixes

• Include badge for latest pub.dev version in each package README (44f6e9d)

microsoft_kiota_bundle: 0.0.2

0.0.2 (2025-01-09)

Bug Fixes

• Include badge for latest pub.dev version in each package README (44f6e9d)

microsoft_kiota_http: 0.0.2

0.0.2 (2025-01-09)

Bug Fixes

• Include badge for latest pub.dev version in each package README (44f6e9d)

microsoft_kiota_serialization_form: 0.0.2

0.0.2 (2025-01-09)

Bug Fixes

• Include badge for latest pub.dev version in each package README (44f6e9d)

microsoft_kiota_serialization_json: 0.0.2

0.0.2 (2025-01-09)

Bug Fixes

• Include badge for latest pub.dev version in each package README (44f6e9d)

microsoft_kiota_serialization_multipart: 0.0.2

0.0.2 (2025-01-09)

Bug Fixes

• Include badge for latest pub.dev version in each package README (44f6e9d)

microsoft_kiota_serialization_text: 0.0.2

0.0.2 (2025-01-09)

Bug Fixes

• Include badge for latest pub.dev version in each package README (44f6e9d)

---

This PR was generated with Release Please. See documentation.

[baywet]

@andrueastman for some reason the bot is not creating the PRs even though it works fine with the CLI.
I was wondering if you could take a look at the configuration here, I know you've solved similar init problems in the past.
Also @Ndiritu.

Thanks @ricardoboss for the help all along.

[andrueastman]

Closing this temporarily to perform a test.

[andrueastman]

@baywet Not sure what I did there but looks like #77 was created after I closed this PR and cleaned up the labels.

Then I applied the release-please:force-run to the last PR merged and looks like it triggered. Maybe we can monitor if the trigger issue re-occurs on the next release?

[baywet]

Thank you for landing some of your magic release please powers!!!