Skip to content

chore(release): bump versions#132

Merged
fu050409 merged 1 commit into
mainfrom
release
Mar 29, 2026
Merged

chore(release): bump versions#132
fu050409 merged 1 commit into
mainfrom
release

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Mar 29, 2026

Releases

dropout

v0.2.0-alpha.6

Refactors

New Features

Chores

@dropout/docs

v0.1.0-alpha.1

Chores

@dropout/ui

v0.1.0-alpha.4

Chores

Refactors

New Features

@vercel
Copy link
Copy Markdown

vercel Bot commented Mar 29, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
drop-out-docs Ready Ready Preview, Comment Mar 29, 2026 2:27pm

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Mar 29, 2026

Reviewer's Guide

Release housekeeping PR that bumps package versions for @dropout/docs and @dropout/ui, adds/updates their changelogs for the new alpha releases, and deletes the now-consumed .changes entry files.

File-Level Changes

Change Details Files
Bump package versions for docs and UI to new alpha releases.
  • Update @dropout/docs version from 0.1.0-alpha to 0.1.0-alpha.1 in its package manifest.
  • Update @dropout/ui version from 0.1.0-alpha.3 to 0.1.0-alpha.4 in its package manifest.
packages/docs/package.json
packages/ui/package.json
Add and update changelog entries for the new releases.
  • Create a new CHANGELOG for @dropout/docs with a 0.1.0-alpha.1 “Chores” entry referencing the docs lint fixes commit.
  • Prepend a 0.1.0-alpha.4 section to the @dropout/ui changelog documenting new features, refactors, and chores with links to the corresponding commits and PRs.
packages/docs/CHANGELOG.md
packages/ui/CHANGELOG.md
Remove processed changeset metadata files now captured in changelogs.
  • Delete the individual .changes markdown files corresponding to docs lint, store removal, instance create rewrite, game store refactor, particle background rewrite, effect check rewrite, and vite/tauri integration.
.changes/docs-lint.md
.changes/effect-check.md
.changes/game-store.md
.changes/particle-background.md
.changes/remove-store.md
.changes/rewrite-instance-create.md
.changes/vite-tauri.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

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

Hey - I've found 4 issues

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="packages/ui/CHANGELOG.md" line_range="7" />
<code_context>
+
+### New Features
+
+- [`32a4d85`](https://github.com/HydroRoll-Team/DropOut/commit/32a4d85af937e4fd882fa671aee8b72878cc564f): Remove all legacy codes in `stores/`. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
+
+### Refactors
</code_context>
<issue_to_address>
**suggestion (typo):** Consider changing "legacy codes" to "legacy code" for more natural phrasing.

Here, "code" functions as an uncountable noun, so the singular form is standard English usage.

```suggestion
- [`32a4d85`](https://github.com/HydroRoll-Team/DropOut/commit/32a4d85af937e4fd882fa671aee8b72878cc564f): Remove all legacy code in `stores/`. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
```
</issue_to_address>

### Comment 2
<location path="packages/ui/CHANGELOG.md" line_range="11" />
<code_context>
+
+### Refactors
+
+- [`5b799a1`](https://github.com/HydroRoll-Team/DropOut/commit/5b799a125a970e5e56f29a08b3c86450855fb6c4): Full rewrite instance create with stepper page instead of modal. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
+- [`ffbfce8`](https://github.com/HydroRoll-Team/DropOut/commit/ffbfce895c37e8e8306d426a2e59e73647ed6a86): Refactor game store and rename `HomePage` component. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
+- [`18aceb4`](https://github.com/HydroRoll-Team/DropOut/commit/18aceb4ddf01e964d0b81a4e926e42b72c64e355): Rewrite `ParticleBackground` to modern component design instead of global `window` api call. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
</code_context>
<issue_to_address>
**suggestion (typo):** Sentence structure here is a bit awkward; consider rephrasing for clarity.

For example: "Full rewrite of instance creation with a stepper page instead of a modal."

```suggestion
- [`5b799a1`](https://github.com/HydroRoll-Team/DropOut/commit/5b799a125a970e5e56f29a08b3c86450855fb6c4): Full rewrite of instance creation with a stepper page instead of a modal. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
```
</issue_to_address>

### Comment 3
<location path="packages/ui/CHANGELOG.md" line_range="13" />
<code_context>
+
+- [`5b799a1`](https://github.com/HydroRoll-Team/DropOut/commit/5b799a125a970e5e56f29a08b3c86450855fb6c4): Full rewrite instance create with stepper page instead of modal. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
+- [`ffbfce8`](https://github.com/HydroRoll-Team/DropOut/commit/ffbfce895c37e8e8306d426a2e59e73647ed6a86): Refactor game store and rename `HomePage` component. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
+- [`18aceb4`](https://github.com/HydroRoll-Team/DropOut/commit/18aceb4ddf01e964d0b81a4e926e42b72c64e355): Rewrite `ParticleBackground` to modern component design instead of global `window` api call. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
+- [`97fe504`](https://github.com/HydroRoll-Team/DropOut/commit/97fe5046f68b5e4ee5f750945bcc39a27f5eb37b): Rewrite effect instance nullish checking. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
+
</code_context>
<issue_to_address>
**nitpick (typo):** Tweak wording and capitalization around "modern component design" and "API".

Consider: "Rewrite `ParticleBackground` to a modern component design instead of a global `window` API call."

```suggestion
- [`18aceb4`](https://github.com/HydroRoll-Team/DropOut/commit/18aceb4ddf01e964d0b81a4e926e42b72c64e355): Rewrite `ParticleBackground` to a modern component design instead of a global `window` API call. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
```
</issue_to_address>

### Comment 4
<location path="packages/ui/CHANGELOG.md" line_range="18" />
<code_context>
+
+### Chores
+
+- [`ef478b2`](https://github.com/HydroRoll-Team/DropOut/commit/ef478b29605afbd1c3ec88184b64960e8ad01e71): Fix vite config to integrate with Tauri. ([#128](https://github.com/HydroRoll-Team/DropOut/pull/128) by @fu050409)
+
 ## v0.1.0-alpha.3
</code_context>
<issue_to_address>
**nitpick (typo):** Capitalize "Vite" to match the official project name.

Specifically in this line: `Fix vite config to integrate with Tauri.`

```suggestion
- [`ef478b2`](https://github.com/HydroRoll-Team/DropOut/commit/ef478b29605afbd1c3ec88184b64960e8ad01e71): Fix Vite config to integrate with Tauri. ([#128](https://github.com/HydroRoll-Team/DropOut/pull/128) by @fu050409)
```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment thread packages/ui/CHANGELOG.md Outdated

### New Features

- [`32a4d85`](https://github.com/HydroRoll-Team/DropOut/commit/32a4d85af937e4fd882fa671aee8b72878cc564f): Remove all legacy codes in `stores/`. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

suggestion (typo): Consider changing "legacy codes" to "legacy code" for more natural phrasing.

Here, "code" functions as an uncountable noun, so the singular form is standard English usage.

Suggested change
- [`32a4d85`](https://github.com/HydroRoll-Team/DropOut/commit/32a4d85af937e4fd882fa671aee8b72878cc564f): Remove all legacy codes in `stores/`. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
- [`32a4d85`](https://github.com/HydroRoll-Team/DropOut/commit/32a4d85af937e4fd882fa671aee8b72878cc564f): Remove all legacy code in `stores/`. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)

Comment thread packages/ui/CHANGELOG.md

### Refactors

- [`5b799a1`](https://github.com/HydroRoll-Team/DropOut/commit/5b799a125a970e5e56f29a08b3c86450855fb6c4): Full rewrite instance create with stepper page instead of modal. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

suggestion (typo): Sentence structure here is a bit awkward; consider rephrasing for clarity.

For example: "Full rewrite of instance creation with a stepper page instead of a modal."

Suggested change
- [`5b799a1`](https://github.com/HydroRoll-Team/DropOut/commit/5b799a125a970e5e56f29a08b3c86450855fb6c4): Full rewrite instance create with stepper page instead of modal. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
- [`5b799a1`](https://github.com/HydroRoll-Team/DropOut/commit/5b799a125a970e5e56f29a08b3c86450855fb6c4): Full rewrite of instance creation with a stepper page instead of a modal. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)

Comment thread packages/ui/CHANGELOG.md

- [`5b799a1`](https://github.com/HydroRoll-Team/DropOut/commit/5b799a125a970e5e56f29a08b3c86450855fb6c4): Full rewrite instance create with stepper page instead of modal. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
- [`ffbfce8`](https://github.com/HydroRoll-Team/DropOut/commit/ffbfce895c37e8e8306d426a2e59e73647ed6a86): Refactor game store and rename `HomePage` component. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
- [`18aceb4`](https://github.com/HydroRoll-Team/DropOut/commit/18aceb4ddf01e964d0b81a4e926e42b72c64e355): Rewrite `ParticleBackground` to modern component design instead of global `window` api call. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nitpick (typo): Tweak wording and capitalization around "modern component design" and "API".

Consider: "Rewrite ParticleBackground to a modern component design instead of a global window API call."

Suggested change
- [`18aceb4`](https://github.com/HydroRoll-Team/DropOut/commit/18aceb4ddf01e964d0b81a4e926e42b72c64e355): Rewrite `ParticleBackground` to modern component design instead of global `window` api call. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)
- [`18aceb4`](https://github.com/HydroRoll-Team/DropOut/commit/18aceb4ddf01e964d0b81a4e926e42b72c64e355): Rewrite `ParticleBackground` to a modern component design instead of a global `window` API call. ([#129](https://github.com/HydroRoll-Team/DropOut/pull/129) by @fu050409)

Comment thread packages/ui/CHANGELOG.md Outdated

### Chores

- [`ef478b2`](https://github.com/HydroRoll-Team/DropOut/commit/ef478b29605afbd1c3ec88184b64960e8ad01e71): Fix vite config to integrate with Tauri. ([#128](https://github.com/HydroRoll-Team/DropOut/pull/128) by @fu050409)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nitpick (typo): Capitalize "Vite" to match the official project name.

Specifically in this line: Fix vite config to integrate with Tauri.

Suggested change
- [`ef478b2`](https://github.com/HydroRoll-Team/DropOut/commit/ef478b29605afbd1c3ec88184b64960e8ad01e71): Fix vite config to integrate with Tauri. ([#128](https://github.com/HydroRoll-Team/DropOut/pull/128) by @fu050409)
- [`ef478b2`](https://github.com/HydroRoll-Team/DropOut/commit/ef478b29605afbd1c3ec88184b64960e8ad01e71): Fix Vite config to integrate with Tauri. ([#128](https://github.com/HydroRoll-Team/DropOut/pull/128) by @fu050409)

@fu050409 fu050409 merged commit c4dc067 into main Mar 29, 2026
4 checks passed
@fu050409 fu050409 deleted the release branch March 29, 2026 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant