Eliminate need for publish-26-release.yaml #171
Labels
good-first-issue
Candidate issues to start contributing to the project
hacktoberfest
Candidate issues to participate in Hacktoberfest
As discussed at https://github.com/jboss-dockerfiles/wildfly/pull/170/files#r1086726562 consider doing and perhaps do something more sophisticated than the #169 fix. I say 'consider' because it's not at all obvious that improving it is cost effective.
The essence of the #169 problem is there is a particular release stream that can be 'latest' and all other streams cannot. And what stream is the 'latest' is evolves over time. So either a clean algorithm for calculating the 'latest' would be necessary, or we update the yaml to change a constant when it changes.
A further twist is which JDK versions are appropriate can vary based on the release stream.
The text was updated successfully, but these errors were encountered: