Skip to content

Unstable release upgrades #6

Closed
Closed
@rarkins

Description

@rarkins
Collaborator

Default behaviour should definitely be that we don't update from stable to unstable. Any project wishing to try an unstable package release should do that manually.

However, if a project is already using an unstable release, they would presumably want access to upgrades, such as from release candidate 1 to release candidate 2 or from a release candidate to final release.

Hence it is a nice-to-have feature that any existing unstable versions are checked for possible upgrades.

Activity

locked as resolved and limited conversation to collaborators on Dec 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @rarkins

        Issue actions

          Unstable release upgrades · Issue #6 · renovatebot/renovate