Support for python 3.14 #184

Activity

1. jbw976 commented on Nov 17, 2025

   

   jbw976

   on Nov 17, 2025

   Member

   More actions

   You've now been invited as an maintainer on this repo @iciclespider - feel free to take this release on if you're up for it! the other function-sdk-python maintainers I'm sure will be happy to support, and I can too if it's not too specific of a python problem 😇
2. iciclespider commented on Nov 17, 2025

   

   iciclespider

   on Nov 17, 2025

   CollaboratorAuthor

   More actions

   I can take on another release. I have a couple of questions:

   1. This PR chore(deps): update dependency protobuf to v6.33.1 #183 might as well get included. At appears to me that I do not have permission to approve or merge. Is that because it was created before I became a maintaner?
   2. Is the release procedure documented somewhere else?
   3. Should this be a v0.9.1 or a v0.10.0?
   4. What branches should be created?
   5. What tags should be created?
   6. Then, to generate the release, I assume one goes to the Releases page and runs "Draft a new release". Is the Changelog manually generated?
3. jbw976 commented on Nov 17, 2025

   

   jbw976

   on Nov 17, 2025

   Member

   More actions

   awesome @iciclespider, thanks for stepping into maintainer duties!

   1. looks like chore(deps): update dependency protobuf to v6.33.1 #183 just needs an official approval before being able to be merged - all PRs need an approval first.
   2. this is probably the best guidance around releasing functions, hopefully nothing is missing, but if so then a PR should be opened to fill that gap: https://docs.crossplane.io/v2.1/guides/extensions-release-process/#quickstart-releasing-a-function-to-xpkgcrossplaneio
   3. i'd vote for a v0.10.0 because I think there's a lot of changes since the v0.9.0 release a few months back
   4. / 5. as per the release guidance docs page, a release-0.10 branch and a v0.10.0 tag would be created in that branch
   5. Yes the change log can be automatically generated by the GitHub draft a new release page, just use the last release tag v0.9.0 as the "last release" comparison

   Let me know if there's any other questions!
4. iciclespider

   closed this as completedin #185on Nov 21, 2025