Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to a different release action #48

Merged
merged 1 commit into from
Oct 13, 2023
Merged

Move to a different release action #48

merged 1 commit into from
Oct 13, 2023

Conversation

pbrisbin
Copy link
Member

@pbrisbin pbrisbin commented May 26, 2023

The way things were before we created a (pulished) release first, then
build and uploaded assets. This meant (particularly with OSX) the
release existed as "latest" for a long time without assets. This causes
issues for anyone that tries to install during this time, including some
test suites.

This new action allows you to create a Draft release, upload assets,
then publish it -- meaning it won't be visible until it's ready, solving
that problem.

Annoyingly, we had to fork the action to do it, as the best one our
there needed a fix and the maintainer is gone.


@pbrisbin pbrisbin changed the title Trying out new release-action Move to a different release action Oct 12, 2023

- [ ] Descriptive, imperative-tense title
- [ ] Body explaining the _why_ of the change
- [ ] `breaking-change` or `enhancement` label applied if appropriate
Copy link
Member Author

@pbrisbin pbrisbin Oct 12, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new release action uses GitHub's automatic release-notes feature and I've included a configuration for sectioning the listed PRs based on labels, hence this prompting to use them.

@pbrisbin
Copy link
Member Author

pbrisbin commented Oct 12, 2023

Example Release:

NOTE: It didn't use the section titles from our release.yml config because it's not on main yet.

The way things were before we created a (pulished) release first, then
build and uploaded assets. This meant (particularly with OSX) the
release existed as "latest" for a long time without assets. This causes
issues for anyone that tries to install during this time, including some
test suites.

This new action allows you to create a Draft release, upload assets,
then publish it -- meaning it won't be visible until it's ready, solving
that problem.

Annoyingly, we had to fork the action to do it, as the best one our
there needed a fix and the maintainer is gone.
@pbrisbin pbrisbin marked this pull request as ready for review October 12, 2023 20:32
@pbrisbin pbrisbin requested a review from a team as a code owner October 12, 2023 20:32
@pbrisbin pbrisbin requested review from joelmccracken and removed request for a team October 12, 2023 20:32
@pbrisbin pbrisbin merged commit 5b4342b into main Oct 13, 2023
2 checks passed
@pbrisbin pbrisbin deleted the pb/release-action branch October 13, 2023 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants