MetaMask / MetaMask/core

It takes time to figure out which packages are being released in a release PR

Open
#4,010 0 comments 0 reactions 0 assignees View on GitHub
team-wallet-framework wf-release-process
Dominant language
TypeScript
Stars
413
Forks
308
Avg merge
1d 4h
Merged PRs (30d)
253

Description

One of the steps involved in approving a release is to look over the dry-run output. Currently this output is not as helpful as it could be as [it lists all packages instead of only the ones that are being released](https://github.com/MetaMask/action-npm-publish/issues/58), so we need to also take a look at the release PR itself to confirm which packages are being released. The way to do this is to go through the PR and check which packages are being bumped, but it would be easier if we didn't have to do this and if we could simply check the PR description instead. It would be even easier if the description for a release PR was updated automatically so that it always reflected the contents of the PR.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the release PR workflow and the dry-run output described in the issue, including the linked action-npm-publish issue. Done means release PR descriptions are updated automatically to show only the packages being released, so approval no longer requires checking package bumps manually.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.