Skip to content

Conversation

@dmannarino
Copy link
Member

Pull request checklist

Please check if your PR fulfills the following requirements:

  • Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
  • Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
  • Check the commit's or even all commits' message styles matches our requested structure.
  • Check your code additions will fail neither code linting checks nor unit test.

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this introduce a breaking change?

  • Yes
  • No

Other information

@dmannarino dmannarino changed the title Upgrade, well, everything (waiting for TF upgrade so we can use modern Python) Upgrade, well, everything (waiting for TF upgrade so we can use modern AWS module) Oct 24, 2025
@dmannarino dmannarino changed the title Upgrade, well, everything (waiting for TF upgrade so we can use modern AWS module) Upgrade almost everything (waiting for TF upgrade so we can use modern AWS module) Oct 24, 2025
@dmannarino dmannarino changed the title Upgrade almost everything (waiting for TF upgrade so we can use modern AWS module) Upgrade almost everything (including AWS module for newer runtimes) Dec 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants