# Robot Framework 7.3 has been released! 🚀

**URL:** <https://forum.robotframework.org/t/robot-framework-7-3-has-been-released/8924>\
**Category:** Robot Framework\
**Created:** [30 May 2025 15:38 UTC](https://forum.robotframework.org/t/robot-framework-7-3-has-been-released/8924 "2025-05-30T15:38:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pekkaklarck](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.robotframework.org/pekkaklarck/32/1019_2.png) [@pekkaklarck](https://forum.robotframework.org/u/pekkaklarck)\
**Post date:** [30 May 2025 15:38 UTC](https://forum.robotframework.org/t/robot-framework-7-3-has-been-released/8924/1 "2025-05-30T15:38:45Z")

</div>

Robot Framework 7.3 is a feature release with variable type conversion (includes also user keyword argument conversion), fixes and enhancements related to timeouts, official Python 3.14 compatibility, and various other exciting new features and high priority bug fixes. For more details about everything that’s new, enhanced and fixed, see the [release notes](https://github.com/robotframework/robotframework/blob/master/doc/releasenotes/rf-7.3.rst).

Robot Framework is developed with support from the Robot Framework Foundation and its 80+ member organizations. Join the journey — support the project by [joining the Foundation](https://robotframework.org/foundation).

Big thanks to the Foundation for their support, to all contributions, and to everyone else who has tested preview releases, submitted bug reports, proposed enhancements, debugged problems, or otherwise helped with Robot Framework 7.3 development!

---

<div class="post-metadata">

**Author:** ![pekkaklarck](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.robotframework.org/pekkaklarck/32/1019_2.png) [@pekkaklarck](https://forum.robotframework.org/u/pekkaklarck)\
**Post date:** [9 June 2025 13:24 UTC](https://forum.robotframework.org/t/robot-framework-7-3-has-been-released/8924/2 "2025-06-09T13:24:50Z")

</div>

Two pretty high priority bugs in the recently released Robot Framework 7.3 has been reported:

> <https://github.com/robotframework/robotframework/issues/5443>
>
> Hey,
> 
> I've been trying out the new Variable Type Conversion feature in RF 7.3 an…d ran into a parsing issue that I think isn't handled correctly.
> 
> Here's a minimal example:
> 
> \`\`\`robot
> \*\*\* Test Cases \*\*\*
> first
> a simple keyword with args 2 a string
> 
> 
> \*\*\* Keywords \*\*\*
> a simple keyword with args
> \[Arguments\] ${a: int}=1 ${b: str}
> Log ${a}
> Log ${b}
> \`\`\`
> 
> In this case, I would expect a proper error like:
> 
> \`\`\`
> Non-default argument after default arguments.
> \`\`\`
> 
> Instead, parsing fails completely with the following error:
> 
> \`\`\`
> \[ERROR \] Parsing '.../variable\_conversion copy.robot' failed: Type information given to non-existing argument 'b'.
> \`\`\`
> 
> If I remove the type from \`${b}\`, the correct error is shown, so the issue seems to be triggered specifically by the type info.
> 
> \`\`\`
> \[ERROR \] Error in file '.../variable\_conversion.robot' on line 8: Creating keyword 'a simple keyword with args' failed: Invalid argument specification: Non-default argument after default arguments.
> \`\`\`
> 
> Cheers!
> Daniel

> <https://github.com/robotframework/robotframework/issues/5444>
>
> I have noticed that following code:
> 
> \`\`\`
> \*\*\* Settings \*\*\*
> Suite Setup Set Var…iables For ${CLUSTER\_TYPE}
> 
> 
> \*\*\* Variables \*\*\*
> ${CLUSTER\_TYPE} Test
> 
> 
> \*\*\* Test Cases \*\*\*
> Do Nothing
> No Operation
> 
> 
> \*\*\* Keywords \*\*\*
> Set Variables For Test
> No Operation
> 
> Set Variables For Dev
> No Operation
> 
> Set Variables For ${environment}
> Fail Did not found setup method for ${environment}.
> 
> \`\`\`
> 
> Works on 7.2.2 but doesn't work on 7.3:
> 
> !\[Image\](https://github.com/user-attachments/assets/43ddc3c7-c331-4963-b94c-76ca67e8403b)
> 
> It appears that previously we first checked for existence of keyword with the given name, but now we check the keywords with embedded variables first. Is this intentional change?

Both of them have already been fixed, and my plan is to create RF 7.3.1 release this week, probably already on Wednesday, to get fixes out relatively soon. If you haven’t yet tested RF 7.3 in your environment, I hope you can do that _now_ so that we get also possible regressions affecting _your_ tests or tasks fixed in RF 7.3.1. There will be a bit longer break before the possible second bug fix release,

---

<div class="post-metadata">

**Author:** ![pekkaklarck](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.robotframework.org/pekkaklarck/32/1019_2.png) [@pekkaklarck](https://forum.robotframework.org/u/pekkaklarck)\
**Post date:** [16 June 2025 15:17 UTC](https://forum.robotframework.org/t/robot-framework-7-3-has-been-released/8924/3 "2025-06-16T15:17:39Z")

</div>

Robot Framework 7.3.1 with fixed to the above issues has been released. For more details see the [release notes](https://github.com/robotframework/robotframework/blob/master/doc/releasenotes/rf-7.3.1.rst).