File tree Expand file tree Collapse file tree 1 file changed +26
-0
lines changed Expand file tree Collapse file tree 1 file changed +26
-0
lines changed Original file line number Diff line number Diff line change 1+ # Cutting releases
2+
3+ While this project is considered unstable/beta quality, the following steps should be taken:
4+
5+ 1 . Ensure all changes are merged and that ` master ` is locally updated.
6+ 2 . Ensure you're logged in as the ` matrixdotorg ` npm user (for at least the project). ` npm whoami ` will tell you this.
7+ 3 . Run ` npm version 0.1.0-beta.15 ` (using whatever beta number is next).
8+ 4 . Push ` master ` and the created ` v0.1.0-beta.15 ` tag
9+ 5 . Run ` npm publish ` to update npm
10+ 6 . Run
` npm dist-tag add [email protected] beta ` to add the
` beta ` tag to the npm release.
11+ 7 . Go to https://github.com/matrix-org/matrix-widget-api/releases/new?tag=v0.1.0-beta.15 and use the following template for the notes:
12+ ```
13+ Changes since v0.1.0-beta.14:
14+
15+ * Add support for disabling modal buttons by default, optionally.
16+ ```
17+
18+ ** Mark the release as a pre-release.**
19+ 8 . Publish the release.
20+
21+ Now, for the consumer update steps:
22+
23+ 1 . ` yarn add matrix-widget-api@beta ` in the react-sdk, likely on the PR branch that is trying to use the updated dependency.
24+ 2 . Push the react-sdk changes to ` develop ` - this is important to keep the lockfile for element-web sane.
25+ 3 . ` yarn add matrix-widget-api@beta ` in element-web, double checking that the lockfile upgraded rather than appended the version.
26+ 4 . Push the element-web changes to ` develop `
You can’t perform that action at this time.
0 commit comments