some of older spring boot migration guides are returning 500 server error today, and there is no alternative source of them:

https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.4-Release-Notes#upgrading-from-spring-boot-23 https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.5-Release-Notes#upgrading-from-spring-boot-24 https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.6-Release-Notes#upgrading-from-spring-boot-25

Comment From: wilkinsona

Thanks for the report but this is a problem on GitHub's side and is out of our control. As the message says, if the problem persists feel free to contact GitHub support.

Comment From: philwebb

Not pretty, but you can still access the raw content using https://raw.githubusercontent.com/wiki/spring-projects/spring-boot/releasenotes/<title>.asciidoc. E.g. https://raw.githubusercontent.com/wiki/spring-projects/spring-boot/releasenotes/Spring-Boot-2.4-Release-Notes.asciidoc

I've raised a support request.

Comment From: yanaair

I contacted support and here's the reply I received, looks like the issue is on your side:

Hi Yana,

Thanks for reaching out to GitHub Premium Support.

When I have seen this in the past it is related to a minor change in the wiki.

I would take a look specifically at these three commits (you have to clone it locally to see them).

* 4b9b17a (HEAD -> master, origin/master, origin/HEAD) Updated Spring Boot 3.1.0 M1 Release Notes (asciidoc)
* 6bb5b57 Updated Spring Boot 3.1.0 M1 Release Notes (asciidoc)
* f81b3f9 Begin 3.1 release notes

What seems to be happening in our build is that there is a missing authored_date for one of the commits, but I can't see which one in the logging.

Using git log --follow Spring-Boot-Config-Data-Migration-Guide.asciidoc I found what is likely the offending commit.

commit 99e10e3e4fccf311330ef0df14ae4d05f42ae1da
Author: Scott Frederick <scottyfred@gmail.com>
Date:   Fri Oct 28 11:51:52 2022 -0500

    Fix links

You can see what changed with the command git diff ef9ac5920aac4f8dbb2d91fbdac5ae32ba5f64f7..99e10e3e4fccf311330ef0df14ae4d05f42ae1da

As a next step, I would revert the change back to commit ef9ac5920aac4f8dbb2d91fbdac5ae32ba5f64f7 and see if things start working again.

Please let me know the results of rolling it back.

Cheers,

J.J.

GitHub Premium Support.

Comment From: yanaair

Issue seems to be gone now. Thanks

Comment From: wilkinsona

Thanks, @yanaair. We haven't made any changes on our side but it's good to hear that it's working again for you.

The response from GitHub support is interesting. Commit ef9ac5920aac4f8dbb2d91fbdac5ae32ba5f64f7 was made on 14/12/2021. Rolling back that far would not have been an option. 99e10e3e4fccf311330ef0df14ae4d05f42ae1da also appears to have an author date (and commit date):

commit 99e10e3e4fccf311330ef0df14ae4d05f42ae1da
Author:     Scott Frederick <scottyfred@gmail.com>
AuthorDate: Fri Oct 28 11:51:52 2022 -0500
Commit:     Scott Frederick <scottyfred@gmail.com>
CommitDate: Fri Oct 28 11:51:52 2022 -0500

    Fix links

Oh well. At least the problem's gone now. Thanks again.