Skip to content

Make the submitted file version 1 when a preprint is accepted - #5619

Merged
mauromsl merged 1 commit into
r-v1.9.xfrom
b-preprint-first-version-1.9
Oct 7, 2026
Merged

mauromsl merged 1 commit into
r-v1.9.xfrom
b-preprint-first-version-1.9

Conversation

@ajrbyers

@ajrbyers ajrbyers commented Oct 7, 2026 •

Copy link
Copy Markdown
Member

When a moderator accepts a preprint that has no version yet, the submitted file now becomes version 1. Before, accepting showed a warning and the moderator had to turn the file into a version by hand first.

What changed

  • Preprint.make_first_version() makes the submission file version 1 if the preprint has no versions. Accepting calls it; an existing version is left alone.
  • The Accept button is shown when there is a submission file, not only when a version exists.
  • The callout on the preprint page explains that the submitted file becomes version 1, and how to use a different file instead.
  • repository/tests/test_first_version.py checks that accepting a preprint with no version makes its submitted file version 1.

@ajrbyers
ajrbyers force-pushed the b-preprint-first-version-1.9 branch from 9fbcadb to f0659a4 Compare October 7, 2026 11:50
@ajrbyers
ajrbyers requested a review from mauromsl October 7, 2026 12:09
@mauromsl
mauromsl merged commit e19a24b into r-v1.9.x Oct 7, 2026
4 checks passed
@mauromsl
mauromsl deleted the b-preprint-first-version-1.9 branch October 7, 2026 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants