Skip to content

chore: release v0.13.15#122

Merged
paperbenni merged 1 commit intomainfrom
release-plz-2026-02-23T09-05-45Z
Feb 23, 2026
Merged

chore: release v0.13.15#122
paperbenni merged 1 commit intomainfrom
release-plz-2026-02-23T09-05-45Z

Conversation

@paperbenni
Copy link
Copy Markdown
Member

@paperbenni paperbenni commented Feb 23, 2026

🤖 New release

  • ins: 0.13.14 -> 0.13.15
Changelog

0.13.15 - 2026-02-23

Fixed

  • fix release thingy


This PR was generated with release-plz.

Summary by CodeRabbit

  • Bug Fixes
    • Fixed a release-related issue.

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai bot commented Feb 23, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR is an automated release bump to v0.13.14 that updates the changelog with the new version entry and associated notes, keeping prior entries intact.

File-Level Changes

Change Details Files
Add changelog entry for the v0.13.14 release and adjust surrounding release notes.
  • Append a new release section for version 0.13.14 with date, Fixed, and Other subsections.
  • Record fixes related to the release process under the new Fixed subsection.
  • Add bullets for streaming-related preview changes and other release metadata under the new Other subsection.
  • Retain existing notes about streaming preview changes while reorganizing them around the new version entry.
CHANGELOG.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

@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 2 issues, and left some high level feedback:

  • The new 0.13.14 changelog section duplicates the existing bullet points under ### Other; consider consolidating these entries so each change is listed only once.
  • The changelog items fix release (hopefully) and fix are vague; consider rewriting them to describe the specific issues addressed so the release notes are more informative.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The new 0.13.14 changelog section duplicates the existing bullet points under `### Other`; consider consolidating these entries so each change is listed only once.
- The changelog items `fix release (hopefully)` and `fix` are vague; consider rewriting them to describe the specific issues addressed so the release notes are more informative.

## Individual Comments

### Comment 1
<location> `CHANGELOG.md:20` </location>
<code_context>
 ### Other

+- release v0.13.14
+- something is deeply wrong with github
+- make mime preview streaming
+- make package previews streaming
</code_context>

<issue_to_address>
**suggestion (typo):** Capitalize "GitHub" consistently with the official product name.

In this bullet, change "github" to "GitHub" to use the correct product branding.

```suggestion
- something is deeply wrong with GitHub
```
</issue_to_address>

### Comment 2
<location> `CHANGELOG.md:21` </location>
<code_context>

+- release v0.13.14
+- something is deeply wrong with github
+- make mime preview streaming
+- make package previews streaming
+- init streaming preview generation
</code_context>

<issue_to_address>
**suggestion (typo):** Use the standard uppercase acronym "MIME" instead of "mime".

As it’s an acronym, please capitalize it as “MIME” here.

```suggestion
- make MIME preview streaming
```
</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.

CHANGELOG.md Outdated
### Other

- release v0.13.14
- something is deeply wrong with github
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

suggestion (typo): Capitalize "GitHub" consistently with the official product name.

In this bullet, change "github" to "GitHub" to use the correct product branding.

Suggested change
- something is deeply wrong with github
- something is deeply wrong with GitHub

CHANGELOG.md Outdated

- release v0.13.14
- something is deeply wrong with github
- make mime preview streaming
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

suggestion (typo): Use the standard uppercase acronym "MIME" instead of "mime".

As it’s an acronym, please capitalize it as “MIME” here.

Suggested change
- make mime preview streaming
- make MIME preview streaming

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Feb 23, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 42bdd22 and 6a731b9.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (2)
  • CHANGELOG.md
  • Cargo.toml

📝 Walkthrough

Walkthrough

Version 0.13.15 is released with a package version bump in Cargo.toml and a corresponding changelog entry documenting a bug fix labeled "fix release thingy."

Changes

Cohort / File(s) Summary
Version Release
Cargo.toml, CHANGELOG.md
Version incremented from 0.13.14 to 0.13.15; new changelog entry added under v0.13.15 with Fixed section containing "fix release thingy".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

🐰 A tiny hop from fourteen to fifteen so bright,
The version marches onward through the night,
A fix is logged with care in scrolls of change,
Release notes flutter—nothing strange!

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title states 'chore: release v0.13.15' but the actual release version in the changeset is v0.13.14, creating a version mismatch. Update the PR title to 'chore: release v0.13.14' to match the actual version bump in CHANGELOG.md, .SRCINFO, and PKGBUILD files.
✅ Passed checks (2 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch release-plz-2026-02-23T09-05-45Z

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
CHANGELOG.md (1)

25-37: ⚠️ Potential issue | 🟡 Minor

Remove the duplicate [0.13.14] release section.

The ## [0.13.14] heading and its body appear twice (lines 10–23 and lines 25–37). The second block is a subset of the first (it is missing the - release v0.13.14 bullet under ### Other). The first block already captures all entries and should be the only one.

🗑️ Proposed fix — remove the duplicate block
-## [0.13.14](https://github.com/instantOS/instantCLI/compare/v0.13.13...v0.13.14) - 2026-02-23
-
-### Fixed
-
-- fix release (hopefully)
-- fix
-
-### Other
-
-- something is deeply wrong with github
-- make mime preview streaming
-- make package previews streaming
-- init streaming preview generation
-
 ## [0.13.13](https://github.com/instantOS/instantCLI/compare/v0.13.12...v0.13.13) - 2026-02-22
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` around lines 25 - 37, The CHANGELOG contains a duplicate
release section titled "## [0.13.14]" — remove the second occurrence (the block
starting with the repeated "## [0.13.14]" that contains "### Fixed" and "###
Other" bullets) so only the first, complete 0.13.14 release block remains;
ensure you keep the first block that includes the "- release v0.13.14" bullet
and delete the later, partial duplicate to avoid repeated headings.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@CHANGELOG.md`:
- Around line 25-37: The CHANGELOG contains a duplicate release section titled
"## [0.13.14]" — remove the second occurrence (the block starting with the
repeated "## [0.13.14]" that contains "### Fixed" and "### Other" bullets) so
only the first, complete 0.13.14 release block remains; ensure you keep the
first block that includes the "- release v0.13.14" bullet and delete the later,
partial duplicate to avoid repeated headings.
ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0f379c5 and b54b3e4.

📒 Files selected for processing (1)
  • CHANGELOG.md

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@pkgbuild/ins/.SRCINFO`:
- Line 18: The srcinfo currently has "sha256sums = SKIP", which leaves the
downloaded archive unverified; run the suggested command (curl -L
https://github.com/instantOS/instantCLI/archive/refs/tags/v0.13.14.tar.gz |
sha256sum) to compute the real SHA256 hex, then replace the "SKIP" value in the
sha256sums field inside .SRCINFO with that checksum so the package verifies the
v0.13.14 tarball; ensure the checksum string exactly matches the sha256sum
output (no extra whitespace) and save the updated .SRCINFO.

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b54b3e4 and 42bdd22.

📒 Files selected for processing (2)
  • pkgbuild/ins/.SRCINFO
  • pkgbuild/ins/PKGBUILD
✅ Files skipped from review due to trivial changes (1)
  • pkgbuild/ins/PKGBUILD

options = !lto
source = ins-0.13.10.tar.gz::https://github.com/instantOS/instantCLI/archive/refs/tags/v0.13.10.tar.gz
source = ins-0.13.14.tar.gz::https://github.com/instantOS/instantCLI/archive/refs/tags/v0.13.14.tar.gz
sha256sums = SKIP
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

sha256sums = SKIP leaves the downloaded archive unverified.

The source artifact just changed to a new tag tarball; this is the right moment to record the real checksum. With SKIP, a silently corrupted or tampered download goes undetected.

Generate the correct value with:

curl -L https://github.com/instantOS/instantCLI/archive/refs/tags/v0.13.14.tar.gz | sha256sum

Then replace SKIP:

🛡️ Proposed fix
-	sha256sums = SKIP
+	sha256sums = <computed-sha256-of-ins-0.13.14.tar.gz>
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@pkgbuild/ins/.SRCINFO` at line 18, The srcinfo currently has "sha256sums =
SKIP", which leaves the downloaded archive unverified; run the suggested command
(curl -L
https://github.com/instantOS/instantCLI/archive/refs/tags/v0.13.14.tar.gz |
sha256sum) to compute the real SHA256 hex, then replace the "SKIP" value in the
sha256sums field inside .SRCINFO with that checksum so the package verifies the
v0.13.14 tarball; ensure the checksum string exactly matches the sha256sum
output (no extra whitespace) and save the updated .SRCINFO.

@paperbenni paperbenni changed the title chore: release v0.13.14 chore: release v0.13.15 Feb 23, 2026
@paperbenni paperbenni force-pushed the release-plz-2026-02-23T09-05-45Z branch from 42bdd22 to 6a731b9 Compare February 23, 2026 23:05
@paperbenni paperbenni merged commit ba1e842 into main Feb 23, 2026
3 of 4 checks passed
This was referenced Feb 24, 2026
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