| Fixed for now: https://github.com/hibernate/hibernate.org/commit/00017a3f087e65450847ba4f2d9029580cf4d280 I think we'll have to find a better approach to generate links to the migration guides if we don't want this problem to show up again. If we keep the current method of pointing to a branch, then when we move 6.0 to the master branch and 5.4 to its own branch, the website will link to the 6.0 migration guide on the 5.4 page... Maybe we could link to the tag corresponding to the latest version instead of the branch? Problem is, tags are inconsistent: some have a .Final suffix, while others don't... Maybe we could just duplicate the .Final tags to new tags without the suffix? |
