Skip to content

Merge branch releases/bump-deps into release - #292

Merged
Hanssen0 merged 3 commits into
releasefrom
releases/bump-deps
Aug 29, 2025
Merged

Merge branch releases/bump-deps into release#292
Hanssen0 merged 3 commits into
releasefrom
releases/bump-deps

Conversation

@Hanssen0

Copy link
Copy Markdown
Member

dependabot Bot and others added 3 commits August 29, 2025 12:41
…dates

Bumps the npm_and_yarn group with 2 updates in the / directory: [@nestjs/common](https://github.com/nestjs/nest/tree/HEAD/packages/common) and [axios](https://github.com/axios/axios).


Updates `@nestjs/common` from 10.4.15 to 10.4.16
- [Release notes](https://github.com/nestjs/nest/releases)
- [Commits](https://github.com/nestjs/nest/commits/v10.4.16/packages/common)

Updates `axios` from 1.7.9 to 1.8.2
- [Release notes](https://github.com/axios/axios/releases)
- [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md)
- [Commits](axios/axios@v1.7.9...v1.8.2)

---
updated-dependencies:
- dependency-name: "@nestjs/common"
  dependency-version: 10.4.16
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: axios
  dependency-version: 1.8.2
  dependency-type: direct:production
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
@changeset-bot

changeset-bot Bot commented Aug 29, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2e8ce9c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@netlify

netlify Bot commented Aug 29, 2025

Copy link
Copy Markdown

Deploy Preview for apiccc ready!

Name Link
🔨 Latest commit 2e8ce9c
🔍 Latest deploy log https://app.netlify.com/projects/apiccc/deploys/68b1314914eb1e0008867bf5
😎 Deploy Preview https://deploy-preview-292--apiccc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 77 (🔴 down 15 from production)
Accessibility: 90 (no change from production)
Best Practices: 92 (no change from production)
SEO: 82 (🔴 down 1 from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Aug 29, 2025

Copy link
Copy Markdown

Deploy Preview for appccc ready!

Name Link
🔨 Latest commit 2e8ce9c
🔍 Latest deploy log https://app.netlify.com/projects/appccc/deploys/68b131499f2a6b0008fb780e
😎 Deploy Preview https://deploy-preview-292--appccc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 71 (🔴 down 8 from production)
Accessibility: 88 (no change from production)
Best Practices: 92 (🔴 down 8 from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Aug 29, 2025

Copy link
Copy Markdown

Deploy Preview for liveccc ready!

Name Link
🔨 Latest commit 2e8ce9c
🔍 Latest deploy log https://app.netlify.com/projects/liveccc/deploys/68b13149dfee8f0008aae8a2
😎 Deploy Preview https://deploy-preview-292--liveccc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 8 (🔴 down 1 from production)
Accessibility: 88 (no change from production)
Best Practices: 92 (🔴 down 8 from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@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.

Summary of Changes

Hello @Hanssen0, 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 significant maintenance update across the monorepo, primarily focusing on upgrading dependencies to their latest versions. It also includes a refactoring of package names for consistency and introduces a new dedicated testing package to improve test infrastructure and ensure module compatibility.

Highlights

  • Extensive Dependency Updates: Numerous packages across the monorepo have had their dependencies and development dependencies updated to newer versions. This includes core libraries, UI frameworks, testing tools, and build tools, ensuring the project utilizes the latest stable versions and benefits from bug fixes and performance improvements.
  • Monorepo Structure Refinement and Package Renaming: Several packages, specifically 'docs', 'examples', and 'faucet', have been renamed to follow a consistent '@ckb-ccc/ccc-*' naming convention. This improves clarity and organization within the monorepo structure.
  • Introduction of Dedicated Test Package: A new 'packages/tests' directory has been added with its own package.json, ESLint, and Prettier configurations, along with CJS/ESM compatibility tests. This centralizes testing logic and ensures module compatibility across different environments.
  • Build and Test Script Adjustments: The root 'package.json' scripts ('test', 'build:prepare', 'build') have been updated to integrate the new 'packages/tests' structure and filter it appropriately during build processes, streamlining the development workflow.
  • Minor Code Adjustments for Library Updates: Small code changes were made in 'packages/core' and 'packages/spore' to adapt to updated library APIs, such as changes in '@noble/hashes' import paths, 'secp256k1.Signature' method calls, and the 'encodeDna' implementation.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize 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 counter productive. 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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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.

@netlify

netlify Bot commented Aug 29, 2025

Copy link
Copy Markdown

Deploy Preview for docsccc ready!

Name Link
🔨 Latest commit 2e8ce9c
🔍 Latest deploy log https://app.netlify.com/projects/docsccc/deploys/68b13149ab7da0000889369c
😎 Deploy Preview https://deploy-preview-292--docsccc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 66 (🔴 down 1 from production)
Accessibility: 88 (no change from production)
Best Practices: 92 (no change from production)
SEO: 92 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@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 primarily focuses on updating dependencies across the monorepo. It also introduces a new test package to verify module resolution for both CommonJS and ESM, and renames several packages for better namespacing. The code changes are mainly adaptations to the updated dependencies, ensuring compatibility. Overall, the changes are well-contained and improve the project's maintenance. I have one suggestion for code simplification.

Comment thread packages/spore/src/dob/api/encode.ts
@Hanssen0
Hanssen0 merged commit 1350670 into release Aug 29, 2025
18 of 19 checks passed
@Hanssen0
Hanssen0 deleted the releases/bump-deps branch August 29, 2025 04:55
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