Skip to content

chore: release v1.7.0#99

Merged
JounQin merged 1 commit intomainfrom
release-plz-2025-04-24T07-49-14Z
Apr 24, 2025
Merged

chore: release v1.7.0#99
JounQin merged 1 commit intomainfrom
release-plz-2025-04-24T07-49-14Z

Conversation

@JounQin
Copy link
Member

@JounQin JounQin commented Apr 24, 2025

🤖 New release

  • unrs_resolver: 1.6.6 -> 1.7.0 (✓ API compatible changes)
Changelog

Features

  • enable no_opt_arch flag for mimalloc-safe on linux-aarch64 (#98)


This PR was generated with release-plz.


Important

Bump unrs_resolver to v1.7.0 with a new feature for mimalloc-safe on linux-aarch64.

  • Version Update:
    • Bump unrs_resolver version from 1.6.6 to 1.7.0 in Cargo.toml and Cargo.lock.
  • Changelog:
    • Add entry for version 1.7.0 in CHANGELOG.md.
    • Feature: Enable no_opt_arch flag for mimalloc-safe on linux-aarch64.

This description was created by Ellipsis for 68801b6. You can customize this summary. It will automatically update as commits are pushed.

Summary by CodeRabbit

  • Chores
    • Updated version number to 1.7.0 across project files.
    • Added a new changelog entry for version 1.7.0.

@JounQin JounQin force-pushed the release-plz-2025-04-24T07-49-14Z branch from 68801b6 to ef34b81 Compare April 24, 2025 07:49
@coderabbitai
Copy link

coderabbitai bot commented Apr 24, 2025

Walkthrough

This update introduces version 1.7.0 of the project. The changelog documents the new release, specifying that the no_opt_arch flag is now enabled for the mimalloc-safe package on the linux-aarch64 platform. Both the Rust and npm package manifests are updated to reflect the new version number. No changes were made to public APIs, dependencies, or other configuration settings.

Changes

File(s) Change Summary
CHANGELOG.md Added release notes for version 1.7.0, documenting the enabling of no_opt_arch for mimalloc-safe on linux-aarch64.
Cargo.toml, npm/package.json Updated package version from 1.6.6 to 1.7.0; no other modifications.

Possibly related PRs

  • chore: release v1.6.0 #68: Updates package version and changelog entries for a previous release, similar to this PR.
  • chore: release v1.6.1 #70: Also addresses changes to the mimalloc allocator on Linux aarch64, but focuses on disabling it, showing a related sequence of allocator configuration changes.

Poem

A hop and a skip, the version hops high,
1.7.0 is here—let’s watch it fly!
Changelog refreshed, with flags set anew,
For mimalloc on aarch64, a tweak just for you.
The numbers march on, the carrots stack tall—
This bunny’s quite proud of this update for all! 🥕✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b7f33e6 and ef34b81.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • CHANGELOG.md (1 hunks)
  • Cargo.toml (1 hunks)
  • npm/package.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Benchmark
  • GitHub Check: Codacy Static Code Analysis
🔇 Additional comments (4)
npm/package.json (2)

3-3: Version bump to 1.7.0
Updated the "version" field from 1.6.6 to 1.7.0 in npm/package.json to align with the new release.


3-3:

Details

❓ Verification inconclusive

Verify no leftover old-version references
Please run a search across the repository to ensure there are no remaining occurrences of 1.6.6 (e.g., in CI configs, docs, or lockfiles).


🏁 Script executed:

#!/bin/bash
# Description: Ensure all old version strings are updated.
rg --fixed-strings "1.6.6"

Length of output: 490


Confirm historical 1.6.6 references in CHANGELOG.md
A repo-wide search for 1.6.6 only returns entries in CHANGELOG.md:

  • CHANGELOG.md:## 1.7.0 – 2025-04-24
  • CHANGELOG.md:## 1.6.6 – 2025-04-23
  • CHANGELOG.md:## 1.6.7 – 2024-04-22
  • CHANGELOG.md:## 1.6.6 – 2024-04-22

If these are intended historical entries or diff links, you can leave them as-is. Otherwise, please update or remove any unintended references.

Cargo.toml (1)

7-7: Version bump to 1.7.0
Updated the version in Cargo.toml from 1.6.6 to 1.7.0. This matches the npm manifest and the changelog entry.

CHANGELOG.md (1)

9-14: Add changelog entry for v1.7.0
The new entry for version 1.7.0 dated 2025-04-24 correctly documents enabling the no_opt_arch flag for mimalloc-safe on linux-aarch64 and links the comparison range v1.6.6...v1.7.0.


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@sonarqubecloud
Copy link

Please retry analysis of this Pull-Request directly on SonarQube Cloud

Copy link

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

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

Important

Looks good to me! 👍

Reviewed everything up to 68801b6 in 47 seconds. Click for details.
  • Reviewed 43 lines of code in 3 files
  • Skipped 0 files when reviewing.
  • Skipped posting 7 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. Cargo.toml:12
  • Draft comment:
    Consider using relative paths for the include field (e.g. "src", "examples", "benches") without a leading '/' as paths are relative to the package directory.
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.
2. Cargo.toml:12
  • Draft comment:
    Consider removing the leading '/' from the include paths (e.g. use "src" instead of "/src") to ensure the paths are interpreted as relative to the package root.
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.
3. CHANGELOG.md:91
  • Draft comment:
    Typographical error: 'pacakge.json' should be corrected to 'package.json'.
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.
4. CHANGELOG.md:474
  • Draft comment:
    Typographical error: In '* (napi) release wasi build', the formatting seems off. Consider changing '(napi)' to '(napi)' for consistency.
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.
5. Cargo.toml:51
  • Draft comment:
    Minor grammatical correction: consider changing "naming things are hard" to "naming things is hard" for better readability.
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.
6. Cargo.toml:54
  • Draft comment:
    Consider revising the comment on line 54 to improve its grammar. For example, change "so both pedantic and nursery is enabled" to "so that both pedantic and nursery are enabled."
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.
7. Cargo.toml:55
  • Draft comment:
    Minor grammatical suggestion: update the comment on line 55 from "if they are either false positives, chaotic, or does not make sense" to "if they are either false positives, chaotic, or do not make sense."
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_aE4BVjoGYSD1Mkrf

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

@codecov
Copy link

codecov bot commented Apr 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.40%. Comparing base (b7f33e6) to head (ef34b81).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #99   +/-   ##
=======================================
  Coverage   93.40%   93.40%           
=======================================
  Files          13       13           
  Lines        2865     2865           
=======================================
  Hits         2676     2676           
  Misses        189      189           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@codspeed-hq
Copy link

codspeed-hq bot commented Apr 24, 2025

CodSpeed Performance Report

Merging #99 will not alter performance

Comparing release-plz-2025-04-24T07-49-14Z (ef34b81) with main (b7f33e6)

Summary

✅ 3 untouched benchmarks

@JounQin JounQin merged commit e63a7e0 into main Apr 24, 2025
23 checks passed
@JounQin JounQin deleted the release-plz-2025-04-24T07-49-14Z branch April 24, 2025 08:04
@coderabbitai coderabbitai bot mentioned this pull request Jun 11, 2025
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