Skip to content

Automate releases #2671

Open
Open
@BDisp

Description

@BDisp

#2668 It's in develop and main branches but not in the release version.

This is the second time I've made this error recently.

Whenever an error occurs the best practice is to find the root cause and fix it in such a way that it can't happen again.

I've been thinking about this and believe the root cause is the process for doing a release involves a bunch of manual steps that are easy to mess up.

The fix, is to automate that. It should be possible to have a GitHub action that does it. Or a script.

This issue is now the issue for tracking a fix.

Metadata

Metadata

Assignees

Labels

build-and-deployIssues regarding to building and deploying Terminal.Gui

Type

Projects

Status

🏗 Approved - In progress

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions