SFML tries to generally not break the API in public versions, and I think overall this makes a lot of sense.
If it were different for some parts of the API, those would need to be clearly identified as unstable. Unfortunately, C++ doesn't natively offer something here, so probably the best fit would be the documentation. So this might be more a discussion about API stability than the sf::Text feature at hand...