Using latest unstable version of a function on a foundry branch when function signature changes

Product Feedback
, ,
1

I’m currently working on a project which is using Foundry Branches. On a Branch we are developing a new version of some Functions. I was able to tag and release the new version and make use of it in a Workshop application, however after modifying the function and re-releasing it the Workshop is unable to pick up the new version of the function properly.

Specifically, when modifying a variable using the function I see the function is using the correct minor version, but when I click into the overview → functions → my function I can see that actually the wrong release version is being used (ie the original release, not the re-release) and I am unable to change the version because the function signature changed.

I think this is a bug in Workshop and the variable should allow me to change the release version of the function when on a foundry branch (or should automatically use the latest version)

2

Hi Benjamin,

Sorry for the late response here. To clarify, was it that you had published a version of your function on the branch, then changed the function signature (i.e. added a new input), released to the same version on your branch, and you are unable to use that new input in the workshop? If so, this is a bug we’ve known about and I can forward the feedback to the appropriate teams. For now, a workaround would be to publish to a different version on your branch (for example, change the major/minor/patch version) and use that in your workshop

3

This seemed to happen regardless of whether or not I changed the function signature. For now I have been bumping the patch version (or changing the function name) as a workaround.