You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Robocorp is transitioning to be Python 1st (https://robocorp.com/blog/python-for-automation-as-code), so, while it'll still support Robot Framework in its platform (because it's a framework that runs on Python), it's no longer pushing forward to develop projects which target Robot Framework specifically (and that includes Robot Framework Language Server).
This means the following for the Robot Framework Language Server: if you need some fix and are willing to make a PR then it'll appear in a release, but otherwise no further fixes or improvements will be added unless someone else from the community steps up to implement it, meaning that it'll stay in Robot Framework 6 and Robot Framework 7 will not be supported (unless someone steps up to do the needed work).
PRs are still accepted and will be reviewed and guidance will be given to anyone that'd like to add something (we hope that existing users do see value in it and want to help in doing the transition to a community-based project).
-- if some company/individual would like to become maintainer of the project, please get in touch.
Security issues will still be tackled at least until February/2025.
-- Note: this affects Robot Framework Language Server, Robocorp Code will still be developed (and improved) as usual (so, those using robot.yaml and conda.yaml will still have support for developing Task Packages and it'll be improved to also support Action Packages for AI actions).
The text was updated successfully, but these errors were encountered:
The VAR syntax from Robot Framework 7.0 isn't working properly with Robot Framework Language Server. When the VAR is created with the new syntax, and you try to access the VAR the ls returns Undefined variable error, but the code runs normally without any issue.
Robocorp is transitioning to be Python 1st (https://robocorp.com/blog/python-for-automation-as-code), so, while it'll still support Robot Framework in its platform (because it's a framework that runs on Python), it's no longer pushing forward to develop projects which target Robot Framework specifically (and that includes Robot Framework Language Server).
See: https://robocorp.com/docs-robot-framework for more details.
This means the following for the
Robot Framework Language Server
: if you need some fix and are willing to make a PR then it'll appear in a release, but otherwise no further fixes or improvements will be added unless someone else from the community steps up to implement it, meaning that it'll stay in Robot Framework 6 and Robot Framework 7 will not be supported (unless someone steps up to do the needed work).PRs are still accepted and will be reviewed and guidance will be given to anyone that'd like to add something (we hope that existing users do see value in it and want to help in doing the transition to a community-based project).
-- if some company/individual would like to become maintainer of the project, please get in touch.
Security issues will still be tackled at least until February/2025.
-- Note: this affects
Robot Framework Language Server
,Robocorp Code
will still be developed (and improved) as usual (so, those usingrobot.yaml
andconda.yaml
will still have support for developing Task Packages and it'll be improved to also support Action Packages for AI actions).The text was updated successfully, but these errors were encountered: