Conversation
|
There was a problem hiding this comment.
Pull request overview
Bumps the Deno package versions across the monorepo for the 1.1.0 release, and updates the documented release process.
Changes:
- Update package versions to
1.1.0in multiplepackages/*/deno.jsonfiles - Promote
@nimbus/eventsourcingdbfrom1.1.0-beta.1to1.1.0 - Adjust
RELEASE.mdinstructions to describe using arelease/<VERSION>branch PR flow
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| packages/utils/deno.json | Bump @nimbus/utils version to 1.1.0. |
| packages/mongodb/deno.json | Bump @nimbus/mongodb version to 1.1.0. |
| packages/hono/deno.json | Bump @nimbus/hono version to 1.1.0. |
| packages/eventsourcingdb/deno.json | Move from beta (1.1.0-beta.1) to stable 1.1.0. |
| packages/core/deno.json | Bump @nimbus/core version to 1.1.0. |
| RELEASE.md | Update release process documentation (needs clarity fix per comment). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ``` | ||
|
|
||
| Push to `main` and create a new release on GitHub from there on the GitHub | ||
| Push to a `release/<VERSION>` branch PR and merge to `main` create a new release on GitHub from there on the GitHub |
There was a problem hiding this comment.
The updated release instruction sentence is hard to parse and seems to be missing punctuation/words ("merge to main create a new release..."). This could confuse the release process. Suggest rephrasing into clear steps, e.g. "Push a release/<VERSION> branch, open a PR, merge to main, then create a GitHub release; the workflow will take care of the rest."
| Push to a `release/<VERSION>` branch PR and merge to `main` create a new release on GitHub from there on the GitHub | |
| Push a `release/<VERSION>` branch and open a pull request. After it is merged into `main`, create a new release on GitHub; the GitHub |
No description provided.