Changelog link leads to a 404

[wujastyk]

JabRef version

Latest development branch build (please note build date below)

Operating system

GNU / Linux

Details on version and operating system

JabRef 5.6--2022-03-11--89d1047 Linux 5.13.0-35-generic amd64 Java 17.0.2 JavaFX 17.0.2-ea+3

Checked with the latest development build

• I made a backup of my libraries before testing the latest development version.
• I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

1. Select help / JabRef resources / view change log
2. Taken to https://github.com/JabRef/jabref/blob/master/CHANGELOG.md
3. 404 message.
4. Should be https://github.com/JabRef/jabref/blob/main/CHANGELOG.md (main, not master)

Appendix

...

Log File

Paste an excerpt of your log file here

[NYH-Dolphin]

Hi, I am a junior student who is learning software engineering, I have successfully build the environment in JabRef and I am wondering whether I can try to solve this problem~

[NYH-Dolphin]

Plus, I find the same problem when the operating system is Windows10

[NYH-Dolphin]

Dear JabRef:
Well, I have located this bug position and create a branch called fix-for-issue-8563 in my own folk repo.
Plus, I would like to propose a new revise suggestion. In your version Tags I found several versions as the following shortcut

As you see v4.0 has 4 subversions, v4.0/v4.0-beta/v4.0-beta2/v4.0-beta3, which means if I use JabRef to check the latest version, it should have driected me into the [version]-[subversion] Tag according to the Version type you specified
However, I write the following testcase but it fails

In your class main/org/jabref/logic/util/Version.java, there must be some revise points, could you let me further revise it in order to fit to perse certain version into correct website link?

[Siedlerchr]

I would propose to debug through the failing Tests and set a breakpoint in Version.parse method

[NYH-Dolphin]

I would propose to debug through the failing Tests and set a breakpoint in Version.parse method

I will do that~ What I mean is that this may be a defect in the JabRef and I am wondering whether I can try to fix it on issue #8563 and then make a pull request?

[Siedlerchr]

Yes sure, as long it's related to the issue it's fine!

[NYH-Dolphin]

hey JabRef~
I almost finish to fix this issue. However, when I try to push it to my branch, the gradlew check is fail and tells me the following message

May I need to update my local JRE version?

It's okay, I have re-setup the environment and my JDK version, and it seems work~