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.

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

Update release instructions #1059

Merged
merged 1 commit into from
Mar 21, 2024
Merged

Update release instructions #1059

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 4 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -411,11 +411,12 @@ yarn version:minor
yarn version:patch
```

Modify the _version tag_ in file `./RELEASE`, to match the new release. Then amend the release commit to include this change:
Modify the _version tag_ in file `./RELEASE`, to match the new release, and similarly update the requested version for the `theia-traceviewer` dependency in both the browser and electron example applications (`examples/electron/package.json` and `examples/browser/package.json`)

Then amend the release commit to include these changes:

```bash
<edit ./RELEASES to update tag>
git add RELEASE && git commit --amend
git add RELEASE examples/electron/package.json examples/browser/package.json && git commit --amend
```

Finally, push the branch and use it to create a PR. When the PR is merged, a GitHub release should be created with auto-generated release notes, as well as a git tag. Then the `publish-latest` CI job should trigger and if everything goes well, publish the new version of the repo's packages to `npm`.
Expand Down
Loading