Backport 'Bump stringio and carrierwave' to v0.27

[alecslupu]

🎩 What? Why?

Backport #12132 to v0.27

♥️ Thank you!

[andreslucena]

It shouldn't happen anything bad, bug just in case: we're also updating other gems here, most notably Rails (from 6.1.6 to 6.1.7.6). Is that intentional? Should we try to only update the ones from the original PR?

[alecslupu]

It shouldn't happen anything bad, bug just in case: we're also updating other gems here, most notably Rails (from 6.1.6 to 6.1.7.6). Is that intentional? Should we try to only update the ones from the original PR?

Well, we do not have stringio in 0.27, and the Gemfiles generated a conflict. The upgrade and others is because we do not have a stict locking policy added to rails. Meaning, if i have 0.27 project i can. In this particular case i had to run bundle update decidim carriervawe just to generate the proper Gemfile.

In the end, those 2 Gemfiles are not used in the end user deployment. We have *.gemspec for that.
As long the pipeline is green, we should be ok.

[andreslucena]

As long the pipeline is green, we should be ok.

OK, as is a patch version I'm ok with letting it slide too