Require pipeline version in i18n messages?
I'm not sure if this would become much of an issue with most pipelines, but there may be instances with some pipelines where the parameters may change between versions of pipelines and their meaning could possibly change between versions (e.g. change in acceptable values).
So it may be a good idea to require the pipeline version to be included in the
messages.properties message key, i.e.
pipeline.parameters.<pipeline>.<pipeline version>.<parameter> so that the messages are specific to a specific version of a pipeline.