Exciting news - Release 300 is here!
The Tulip team has rolled out some fresh updates across multiple features, along with some bug fixes. Check out the release notes and dive into what’s new.
Share your thoughts and questions below 
1 Like
Within Account setting under Connectors the publishing mode is permanently set to “Require manual publishing”.
If I understand correctly, I do not think this is a good idea.
What if there were 100+ Apps using a same connector function and
- you find a bug in the connector function logic and you need to fix it, so that the Apps will behave correctly
Or
- the http/sql server provider decided to change their behavior, so you need to modify the connector function logic so that the Apps will behave the same way as before
We were able to just modify the function before r299 (depending on the setting).
Now from r300, we have to republish all the 100+ Apps. Don’t we?
(And I believe there is no easy way to find out and track which App need republishing)
A couple Community suggestions are included in this release
From @BrianHaselton - Removal of Trigger Shortcuts - Revert change - You are able to quickly see trigger description without clicking into it, and also have the previous behavior of cut/copy showing up on hover
From @emendoza - Increase Automation logic blocks - the limit of automation blocks has now increased from 50 to 100!
Thanks folks for the great feedback and helping to make Tulip better as always!
@ta-aoki - I am checking with the team on your question / feedback here. We will get back to you shortly!
3 Likes
Hey @ta-aoki -
A couple comments - This setting only applies to the connector environment, which includes things like the host url, authentication information, and headers that apply across all functions. So any changes to functons maintain the same behavior that they had ahead of this release.
We will be swapping this setting to not require manual publishing for environment settings in a coming release (so changes will always be automatically published without needing to republish apps). To ensure only safe changes are made, we have also added more permissions to customer user roles so you can gate who can make these changes, seeing as they will impact production immedately.
Thanks for the feedback-
Pete
3 Likes
Thank you for pointing out that it only applys to the connector environment.
Thank you also for the information that Tulip is planning to not require manual publishing in a coming release. I am very glad to hear that plan.
I wonder why Tulip have set the r300 with the mode “Require manual publishing” permanently, which is completely opposite from the plan.
Hey @ta-aoki -
The goal here was just to split this work - require manual publishing has been the default since day one for this setting, and has not been changed by ~90% of our customer base. With 300 we released the locking of this setting, but we will be swapping it setting in just a couple weeks. We had planned to do these tasks together, but the holidays interrupted our engineering efforts!
Thanks for your patience-
Pete
2 Likes