Skip to content

New packages fail #7

Description

@david-orn

When trying to deploy a new package this action fails because there is no previous version number that can be found.

This means that when creating a new repository one must first publish a package manually or disable this action. And only after the repository exists can the action be used.

I'd argue that the first package should be set to 0.1.0 rather than failing, making the process of creating new code artifact repositories easier.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions