-
Notifications
You must be signed in to change notification settings - Fork 19
chore(docs): Fix changelog #2642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(docs): Fix changelog #2642
Conversation
…hub.com:opentdf/platform into release-please--branches--main--components--sdk
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @c-r33d, 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 addresses a chore to fix the SDK v0.7 changelog. The primary goal is to ensure the changelog accurately reflects the features and bug fixes included in the SDK's 0.7.0 release. This involves updating version numbers across relevant configuration and source files, and explicitly documenting dependency updates within the changelog itself.
Highlights
- Release Manifest Update: The 'sdk' version in the release-please manifest was incremented from '0.6.1' to '0.7.0'.
- Changelog Entry for SDK v0.7.0: A new entry for version '0.7.0' was added to the SDK's changelog, detailing dependency updates for Docker and the internal 'protocol/go' module.
- SDK Version Constant Update: The internal version constant in 'sdk/version.go' was synchronized to '0.7.0', aligning it with the new release.
- New Release Manifest File: A new '.release-please-manifest.json' file was introduced, containing initial versioning for several components.
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.
Versions advance, Changelog tells what is new, Code evolves on.
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.
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 aims to fix the changelog for the SDK v0.7.0 release. The changes correctly update the version in sdk/version.go
and .github/release-please/release-please-manifest.json
, and clean up the sdk/CHANGELOG.md
. However, a new manifest file, .release-please-manifest.json
, has been added to the root of the repository. This file contains outdated version information and seems to have been added by mistake. It should be removed to avoid potential issues with the release process.
Benchmark results, click to expandBenchmark authorization.GetDecisions Results:
Benchmark authorization.v2.GetMultiResourceDecision Results:
Standard Benchmark Metrics Skipped or FailedBulk Benchmark Results
TDF3 Benchmark Results:
NANOTDF Benchmark Results:
|
Benchmark results, click to expandBenchmark authorization.GetDecisions Results:
Benchmark authorization.v2.GetMultiResourceDecision Results:
Standard Benchmark Metrics Skipped or FailedBulk Benchmark Results
TDF3 Benchmark Results:
NANOTDF Benchmark Results:
|
393ae17
to
fa5d134
Compare
…hub.com:opentdf/platform into fix-changlog-sdk-v07
Invalidated by push of 4125e8e
Benchmark results, click to expandBenchmark authorization.GetDecisions Results:
Benchmark authorization.v2.GetMultiResourceDecision Results:
Standard Benchmark Metrics Skipped or FailedBulk Benchmark Results
TDF3 Benchmark Results:
NANOTDF Benchmark Results:
|
bbf59c3
into
release-please--branches--main--components--sdk
Proposed Changes
1.) SDK release v0.7 changelog had additional features/bugs that were fixed in previous releases.
Checklist
Testing Instructions