Skip to content

chore: add winget steps to release checklist #451

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.

Sign up for GitHub

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

Merged
amoeba merged 3 commits into from
Jul 31, 2026
Merged

chore: add winget steps to release checklist #451

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cf10fc0
update release checklist
amoeba Jul 28, 2026
324ddf5
fix
amoeba Jul 28, 2026
cb082aa
Update RELEASE.md
amoeba Jul 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 20 additions & 1 deletion RELEASE.md
View file
Open in desktop

@eitsupi eitsupi Jul 28, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

IIUC, we shouldn't need to use Komac from our local machine anymore.
If #379 works correctly, a new branch will be created at https://github.com/columnar-tech/winget-pkgs, and we can then open a pull request upstream from that branch.

@amoeba amoeba Jul 29, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Oh, right! I'll update the checklist. Thanks for reminding me.

@eitsupi eitsupi Jul 29, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

(I believe this setting has never used before, so it might fail the first time and we should run Komac for recovery.)

@amoeba amoeba Jul 29, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

How's cb082aa?

@eitsupi eitsupi Jul 29, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good!

@amoeba amoeba Jul 29, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

(I believe this setting has never used before, so it might fail the first time and we should run Komac for recovery.)

k, noted.

Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ $ git push --tags

The automation will take over from the tag being pushed.

## Release Checklist
## Release Pre-Flight Checklist

Before creating and pushing the tags, please consult the following
checklist of steps:
Expand All @@ -54,3 +54,22 @@ checklist of steps:

Once the above checklist is completed, just push the new tag to
kick off the release process.
Then, continue to the [Post-Release Checklist](#post-release-checklist).

## Post-Release Checklist

- [ ] Create a pull request against [microsoft/winget-pkgs](https://github.com/microsoft/winget-pkgs) from [our fork](https://github.com/columnar-tech/winget-pkgs). See [winget](#winget) for details.

### Details

You can find detailed steps for items in the post-release checklist here.

#### winget

Updating our WinGet package is only partially automated. goreleaser automatically creates a branch at https://github.com/columnar-tech/winget-pkgs but then someone needs to manually create a pull request against upstream with the change.

Follow these steps:

1. Wait for the release workflow to finish.
1. Find the branch at https://github.com/columnar-tech/winget-pkgs. It should be called `dbc-$VERSION`.
1. Create a pull request
Loading