chore(build-fix1): release root 0.4.0 #642
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary of Changes
Hello @el-virt, 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 represents the automated release of version 0.4.0 for the opentdf/web-sdk project. It consolidates a substantial collection of new features and critical bug fixes across the SDK, CLI, and core components, significantly enhancing the project's capabilities, stability, and compatibility. The changes aim to provide a more robust and feature-rich experience for users of the OpenTDF web SDK.
Highlights
- Version Bump: This pull request performs an automated release, bumping the root project version and all associated packages (
@opentdf/sdk,@opentdf/ctl,web-app) from0.3.2to0.4.0. - New Features: A significant number of new features have been integrated, including enhanced assertion signing and verification, new CLI options (e.g.,
--allowList,--policyBinding ecdsa), experimental EC support in KAOs, improved platform URL handling, and various SDK enhancements like theOpenTDF.openmethod, custom KAO array templates, and support for connect RPC calls. - Bug Fixes and Improvements: Numerous bug fixes are included, addressing issues such as
npm auditvulnerabilities, CI pipeline stability, regex pattern efficiency, concurrent rewrap handling, NanoTDF specific fixes (KID storage, ECDSA binding), and updates to dependency versions (e.g.,jose6.x,koa,uuid). Compatibility with older platforms and legacy SDK modes has also been improved. - Dependency and Build Updates: The PR updates internal version references across
package.jsonfiles,Makefile, andversion.ts, and generates a comprehensiveCHANGELOG.mddetailing all changes since the previous release.
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 is currently in preview and 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 to provide feedback.
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
-
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. ↩
There was a problem hiding this comment.
Code Review
This pull request primarily updates version numbers across various package configuration files and the Makefile to 0.4.0, reflecting a new release. The changes appear consistent with the release objective. One minor observation is a hardcoded reference to the previous version (0.3.2) within the rebuild script in web-app/package.json (line 17), which ideally should be updated to 0.4.0 to ensure future consistency. However, as this specific line was not part of the direct changes in the provided diff, a line-specific comment cannot be made.
el-virt
deleted the
release-please--branches--build-fix1--components--root
branch
|
🤖 I have created a release beep boop
0.4.0 (2025-06-20)
Features
--policyBinding ecdsaoption (#352) (4e54c0d)Bug Fixes
This PR was generated with Release Please. See documentation.