Upgrade folio-service-tools to RMB 33.x

we use snapshot versions of unreleased folio-libraries and change them to released version while working on module release.

Ok, thank you for your guidance. My understanding was that FOLIO's (admittedly informal) policy was to not use SNAPSHOT dependencies on the mainline of repositories. I guess I need to take that approach as well, in order not to block mod-users. I'm not keen on this because SNAPSHOT dependencies lead to non-repeatable builds.

(I think it might be worth FOLIO considering making all of the shared libraries (including client libraries) part of the limit applied to Stripes, Okapi, RMB and Spring Way)

cc:

, we use snapshot versions of unreleased folio-libraries and change them to released version while working on module release.

I assume that release will be planned for the next sprint. Also, mod-users uses folio-custom-fields that also will be upgraded to the new RMB version.

As I understand it, the development freeze for Core Platform modules is the end of this week. Prior to this, modules are expected to have upgraded to the new RMB version.

My assumption is that they cannot do that, without releases of folio-service-tools (and folio-custom-fields). Have I misunderstood that, or is the intention that modules be changed to use snapshot versions and then need to be changed to the release version after the development freeze?

Can you help me understand how that will work in practice?

cc:

, I assume that release will be planned for the next sprint. Also, mod-users uses folio-custom-fields that also will be upgraded to the new RMB version.

cc:

When is an updated version of folio-service-tools going to be released?

I'm asking because mod-users uses this library and hence needs a new release in order to be upgraded to RMB 33.