Skip to content

Developer's Guide: Bumping version numbers #8795

@kcondon

Description

@kcondon

The steps for bumping version numbers have changed:
-scripts/database/releases.txt is no longer updated, this has been true for a long time, since flyway was introduced.
-the example github commit showing changes contains the old way to update pom.xml, though the page has updated the pom file to be: modules/dataverse-parent/pom.xml -> -> and has a note: Note: the version has been moved to a property in parent module since this commit was created. Just not sure what that means, now that I'm one release away from that. Is there an action required or is it automatically populated?

Note: from last version bump, appears a new/different place to update pom.xml:
3943aa0

modules/dataverse-parent/pom.xml

5.10.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions