Skip to content

Protect releases in some way. #158

Open
@LaurentDhont

Description

@LaurentDhont

When creating releases on a private repo they cannot be seen. Obviously hazel has access to the token so it can (this is necaserry to ship the updates) but anyway with the link can go ahead and download a release (from the hazel deployment).
Is there any way to protect this?

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

    Issue actions