Closed bollwyvl closed 4 years ago
Yes, RF 3.2 requires changes for robotkernel (the old parser in RF is no more) and I’m only half-way there.
no worries. just doing what chores i can :P
On Tue, Nov 26, 2019 at 5:59 PM Asko Soukka notifications@github.com wrote:
Yes, RF 3.2 requires changes for robotkernel (the old parser in RF is no more) and I’m only half-way there.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/robots-from-jupyter/robotlab/pull/58?email_source=notifications&email_token=AAALCRFB66343KGVFN3LDYLQVWS53A5CNFSM4JR6Y522YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFHW5BQ#issuecomment-558853766, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALCRBQD5O7TO6DFR6OZ3TQVWS53ANCNFSM4JR6Y52Q .
Oooh, new deprecations:
[ WARN ] Accessing variable items using '&{FIREFOX}[${OS}]' syntax is deprecated. Use '${FIREFOX}[${OS}]' instead.
I got a second thought about RF 3.2a1. I have updated robotkernel to support 3.2a1, but it's better to still make 2019.12 release with robotframework 3.1.2. I split this into
just starts rolling some versions for #57.
Locally stuff dying during acceptance tests, as no doubt you would expect (I haven't looked into the API changes):
But hey, stuff is building! Let's see what CI turns up that I don't expect...