Skip to content

Conversation

@Siedlerchr
Copy link
Member

Mandatory checks

  • Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
  • Tests created for changes (if applicable)
  • Manually tested changed features in running JabRef (always required)
  • Screenshots added in PR description (for UI changes)
  • Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
  • Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

@github-actions
Copy link
Contributor

github-actions bot commented Jul 9, 2024

The build for this PR is no longer available. Please visit https://builds.jabref.org/main/ for the latest build.

@Siedlerchr Siedlerchr merged commit 1505137 into main Jul 9, 2024
@Siedlerchr Siedlerchr deleted the Siedlerchr-patch-2 branch July 9, 2024 12:18
@koppor
Copy link
Member

koppor commented Jul 9, 2024

OMG, we forgot to follow this step at https://github.com/JabRef/jabref/wiki/Releasing-a-new-Version.

@koppor koppor added the platform: snap When JabRef is run as a snap on linux label Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

platform: snap When JabRef is run as a snap on linux

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants