chore(build-fix1): release 0.4.0 #643
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 web-sdk. It integrates a substantial collection of new features and critical bug fixes across the CLI, SDK core, and underlying libraries, alongside essential build and dependency updates. The primary impact is a more robust, feature-rich, and secure SDK for web applications.
Highlights
- Automated Release: This pull request is an automated release for version
0.4.0of theweb-sdk, consolidating numerous features and bug fixes accumulated since the0.3.2release. - CLI Enhancements: The Command Line Interface (CLI) has been updated with new capabilities, including support for an
--allowListparameter, a--policyBinding ecdsaoption, experimental EC (Elliptic Curve) in Key Access Objects (KAOs), and improved handling of platform URLs for decrypt operations, ensuring platform KAS (Key Access Server) is added to the allowlist when fetching. - SDK Core Functionality & Cryptography: Significant updates to the SDK include enhanced assertion signing key handling and verification, support for EC-wrapped keys, the introduction of a new
OpenTDF.openmethod, improved KAS list retrieval from the platform, and an upgrade to thejoselibrary (version 6.x) for cryptographic operations. - Policy and ABAC Improvements: The system now supports
kao.schemaVersion, can load ABAC (Attribute-Based Access Control) configurations directly from the policy service, and allows for offline ABAC KAO configurations. Several fixes related to policy binding formats have also been implemented. - Build, CI, and Dependency Updates: The PR includes various
npm audit fixupdates to address security vulnerabilities, improvements to the Continuous Integration (CI) pipeline (e.g.,platform_roundtripand Keycloak Docker integration), and dependency bumps forkoaanduuid. It also updates the preferred Node.js version to 22 and includes ESLint updates.
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 updates the version numbers across the project to 0.4.0. It includes changes to the release manifest, changelog, MakeFile, and package.json files for the CLI, library, and web application. The rebuild script in the web-app package.json should be updated to dynamically reference the current version.
web-app/package.json
Outdated
| "preview": "vite preview", | ||
| "test": "vite build && vitest", | ||
| "test:ui": "vite build && vitest --ui", | ||
| "rebuild": "npm remove @opentdf/sdk && npm add file:../lib/opentdf-sdk-0.3.2.tgz && npm run dev" |
There was a problem hiding this comment.
This rebuild script seems to be referencing a specific version (0.3.2) instead of using the current version. This could lead to issues if the script is not updated when the version changes.
"rebuild": "npm remove @opentdf/sdk && npm add file:../lib/opentdf-sdk-$$(npm view . version).tgz && npm run dev"
el-virt
force-pushed
the
release-please--branches--build-fix1
branch
from
76af072 to
745153b
Compare
el-virt
force-pushed
the
release-please--branches--build-fix1
branch
from
a5e56b3 to
725ba60
Compare
|
eugenioenko
left a comment
eugenioenko
left a comment
There was a problem hiding this comment.
Went with Louie on the code changes and the code flow, looks exactly what we need 🎉
🤖 I have created a release beep boop
0.4.0 (2025-06-25)
Features
--policyBinding ecdsaoption (#352) (4e54c0d)Bug Fixes
This PR was generated with Release Please. See documentation.