Skip to content

chore(main): release 0.8.3#542

Open
tinovyatkin wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

chore(main): release 0.8.3#542
tinovyatkin wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@tinovyatkin

@tinovyatkin tinovyatkin commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

🤖 I have created a release beep boop

0.8.3 (2026-07-21)

Features

  • unify bundling and tree-shaking analysis facts (#468) (21b9cb3)

Bug Fixes

  • add certifi to typos allow list (#456) (9f425ea)
  • ci: work around maturin 1.11+ bin bindings regression (#453) (349ad62)
  • deps: update env_logger to 0.11.10 to deduplicate anstream (#454) (9ef981c)
  • remove bin from platform specific npm packages (1aa8c90)
  • split bundler.rs into directory module (#461) (5d7c6e1)

Performance Improvements

  • use Arc<ModModule> in module AST maps to avoid cloning all ASTs in prepare_modules (#465) (ce6b414)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • Chores
    • Updated the application version to 0.8.3 across release metadata and package configuration.

Copilot AI review requested due to automatic review settings July 20, 2026 01:55
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a routine version release for the project, bumping the version to 0.8.3. It includes the necessary updates to manifest files and the changelog to reflect the latest changes, which include optimizations to module AST handling, CI fixes, and dependency updates.

Highlights

  • Version Bump: Updated the project version from 0.8.2 to 0.8.3 across all configuration files, including Cargo.toml, Cargo.lock, and npm package dependencies.
  • Changelog Update: Added the 0.8.3 release notes to CHANGELOG.md, documenting recent features, bug fixes, and performance improvements.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 62d7de3a-5aa8-4e1d-8118-9b9dea554a8c

📥 Commits

Reviewing files that changed from the base of the PR and between 827b2d3 and 5faad1c.

⛔ Files ignored due to path filters (3)
  • CHANGELOG.md is excluded by !CHANGELOG.md
  • Cargo.lock is excluded by !**/*.lock
  • npm/cribo/package.json is excluded by !npm/cribo/package.json
📒 Files selected for processing (3)
  • .release-please-manifest.json
  • Cargo.toml
  • version.txt

📝 Walkthrough

Walkthrough

The release manifest, Cargo workspace package, and version.txt were updated from version 0.8.2 to 0.8.3.

Changes

Release versioning

Layer / File(s) Summary
Synchronize release version records
.release-please-manifest.json, Cargo.toml, version.txt
The release manifest, workspace package, and recorded version were changed from 0.8.2 to 0.8.3.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested labels: autorelease: pending

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely matches the version release bump to 0.8.3.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-please--branches--main

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.

@gemini-code-assist gemini-code-assist Bot left a comment

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.

Code Review

This pull request bumps the version of the cribo package from 0.8.2 to 0.8.3 across multiple configuration files, including Cargo.toml, Cargo.lock, package.json, and version.txt, and updates the CHANGELOG.md with the release notes for this version. All review comments were filtered out as they commented on non-code changes (version numbers), so there is no additional feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Copilot AI left a comment

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.

Pull request overview

Release-please generated version bump and release notes update for Cribo v0.8.3, aligning the Rust workspace, lockfile, npm package, and manifest with the new release version.

Changes:

  • Bump version references from 0.8.2 → 0.8.3 across Rust (workspace) and npm packaging metadata.
  • Add 0.8.3 release notes to CHANGELOG.md.
  • Update release-please manifest and version.txt to reflect 0.8.3.

Reviewed changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated no comments.

Show a summary per file
File Description
version.txt Updates the repo version marker to 0.8.3.
npm/cribo/package.json Bumps npm package version and platform optional dependency versions to 0.8.3.
CHANGELOG.md Adds the 0.8.3 release entry with features/fixes/perf notes.
Cargo.toml Bumps the Rust workspace package version to 0.8.3.
Cargo.lock Updates the resolved workspace package version to 0.8.3.
.release-please-manifest.json Updates release-please manifest version to 0.8.3.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@github-actions

github-actions Bot commented Jul 20, 2026

Copy link
Copy Markdown

📊 Ecosystem Test Results

📋 Test Status

Test Summary:

  • Total: 49
  • ✅ Passed: 48
  • ❌ Failed: 0
  • ⚠️ Errors: 0
  • ⏭️ Skipped: 1

📈 Benchmark Results

📊 View detailed benchmark report

📦 Package Bundling Metrics
Package Bundle Time Bundle Size
httpx 211.84 ms 321 KB
idna 46.63 ms 244.96 KB
pyyaml 177.91 ms 237.6 KB
requests 136.84 ms 216.8 KB
rich 837.04 ms 943.23 KB

Benchmark metrics are tracked via Bencher.dev

📊 View detailed performance trends and comparisons on the Bencher dashboard.

Generated by ecosystem-tests workflow

coderabbitai[bot]
coderabbitai Bot previously approved these changes Jul 20, 2026
@github-actions

github-actions Bot commented Jul 20, 2026

Copy link
Copy Markdown

🐰 Bencher Report

Projectcribo
Branchrelease-please--branches--main
Testbedubuntu-latest
Click to view all benchmark results
BenchmarkLatencyBenchmark Result
nanoseconds (ns)
(Result Δ%)
Upper Boundary
nanoseconds (ns)
(Limit %)
build_dependency_graph📈 view plot
🚷 view threshold
654.05 ns
(-87.11%)Baseline: 5,074.00 ns
14,947.87 ns
(4.38%)
bundle_simple_project📈 view plot
🚷 view threshold
1,426,400.00 ns
(-8.65%)Baseline: 1,561,410.62 ns
5,202,929.45 ns
(27.42%)
resolve_module_path📈 view plot
🚷 view threshold
119.01 ns
(+7.65%)Baseline: 110.55 ns
147.53 ns
(80.67%)
🐰 View full continuous benchmarking report in Bencher

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5faad1c4fc

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread Cargo.toml
license = "MIT"
repository = "https://github.com/ophidiarium/cribo"
version = "0.8.2"
version = "0.8.3"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Bump to an unused release version

This sets the package version to 0.8.3 even though this repository already has prior release commits for 0.8.3 (04a49f1) and even 0.8.4 (84fe47b) with the same Cargo/npm package versions. When the release workflow builds from this tag, the package registries and/or an existing v0.8.3 tag will collide with the earlier release, and the PyPI/npm jobs are configured to skip existing versions, so users would keep getting the old 0.8.3 artifacts instead of this release. Please advance the release metadata to the next unused version rather than reusing 0.8.3.

Useful? React with 👍 / 👎.

Comment thread CHANGELOG.md

### Features

* unify bundling and tree-shaking analysis facts ([#468](https://github.com/ophi-dev/cribo/issues/468)) ([21b9cb3](https://github.com/ophi-dev/cribo/commit/21b9cb37bee6a89065a5175322f1d868afc4f659))

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Regenerate the stale release notes

This new changelog section lists commits such as 21b9cb3 even though git log f0654cc..9fe1917 contains only this release commit, and the same entry is already present in the 0.8.2 section immediately below. If this release is published with these notes, users will be told that old changes shipped again while the actual changes since 0.8.2 are omitted, so the section should be regenerated from the real release range before merging.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants