-
Notifications
You must be signed in to change notification settings - Fork 3
Comparing changes
Open a pull request
base repository: opentdf/java-sdk
base: v0.8.1
head repository: opentdf/java-sdk
compare: v0.9.0
- 8 commits
- 28 files changed
- 4 contributors
Commits on May 29, 2025
-
chore(main): release 0.8.2-SNAPSHOT (#264)
🤖 I have created a release *beep* *boop* --- <details><summary>0.8.2-SNAPSHOT</summary> ### Updating meta-information for bleeding-edge SNAPSHOT release. </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: opentdf-automation[bot] <149537512+opentdf-automation[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 65ca764 - Browse repository at this point
Copy the full SHA 65ca764View commit details
Commits on May 30, 2025
-
chore(ci): DSPX-850 - Add workflows to support LTS releases (#260)
Co-authored-by: Sean Trantalis <18211470+strantalis@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for a77a401 - Browse repository at this point
Copy the full SHA a77a401View commit details
Commits on Jun 2, 2025
-
Configuration menu - View commit details
-
Copy full SHA for cdb7afe - Browse repository at this point
Copy the full SHA cdb7afeView commit details
Commits on Jun 4, 2025
-
chore(ci): Fix secrets passing for reusable workflows (#266)
Secrets need to be passed to reusable workflows.
Configuration menu - View commit details
-
Copy full SHA for 76b5a9c - Browse repository at this point
Copy the full SHA 76b5a9cView commit details
Commits on Jun 10, 2025
-
chore(ci): Fix release-please workflow (#268)
Move release-please files to standard location to work with `opentdf/platform/.github/workflows/reusable_release-please.yaml`
Configuration menu - View commit details
-
Copy full SHA for 14288d5 - Browse repository at this point
Copy the full SHA 14288d5View commit details
Commits on Jul 10, 2025
-
feat(sdk): Get the algorithm from the KASInfo and not the config (#272)
Instead of taking what's in the config use what's in the key since what we use to actually do the cryptography. Also some refactoring to simplify how we get key metadata.
Configuration menu - View commit details
-
Copy full SHA for feff0e8 - Browse repository at this point
Copy the full SHA feff0e8View commit details
Commits on Jul 14, 2025
-
fix(sdk): upgrade the platform protocol code (#275)
In gateway we are seeing an error like ``` Caused by: com.google.protobuf.InvalidProtocolBufferException: While parsing a protocol message, the input ended unexpectedly in the middle of a field. This could mean either that the input has been truncated or that an embedded message misreported its own length ``` when fetching attributes. [`v2.6.2` of platform contains `v0.5.0` of `protocol/go`](https://github.com/virtru-corp/data-security-platform/blob/v2.6.2/go.mod#L34) and there are changes between the two versions in the attributes. This should at least be safe.
Configuration menu - View commit details
-
Copy full SHA for 90eaba1 - Browse repository at this point
Copy the full SHA 90eaba1View commit details -
chore(main): release 0.9.0 (#274)
🤖 I have created a release *beep* *boop* --- <details><summary>0.9.0</summary> ## [0.9.0](v0.8.1...v0.9.0) (2025-07-14) ### Features * **sdk:** Get the algorithm from the KASInfo and not the config ([#272](#272)) ([feff0e8](feff0e8)) ### Bug Fixes * **sdk:** upgrade the platform protocol code ([#275](#275)) ([90eaba1](90eaba1)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: opentdf-automation[bot] <149537512+opentdf-automation[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 2de6a49 - Browse repository at this point
Copy the full SHA 2de6a49View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.8.1...v0.9.0