From 4d8406fc3f03968275d4bc001acf7522bbe78c8f Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Tue, 9 Jul 2024 16:25:33 -0700 Subject: [PATCH] chore(gradle): bump deephaven-csv from 0.12.0 to 0.14.0 (#5740) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Bumps `deephaven-csv` from 0.12.0 to 0.14.0. Updates `io.deephaven:deephaven-csv` from 0.12.0 to 0.14.0
Release notes

Sourced from io.deephaven:deephaven-csv's releases.

v0.14.0

What's Changed

Full Changelog: https://github.com/deephaven/deephaven-csv/compare/v0.13.0...v0.14.0

v0.13.0

What's Changed

Full Changelog: https://github.com/deephaven/deephaven-csv/compare/v0.12.0...v0.13.0

Changelog

Sourced from io.deephaven:deephaven-csv's changelog.

Release

This document is primarily targeted towards Deephaven CSV release managers. It is meant to contain the necessary instructions for executing a Deephaven CSV release.

Please be sure to read and understand this document in full before proceeding with a release. If you have any questions or concerns about any of the commands, please reach out.

Jar artifacts

The deephaven-csv release process consists of releasing two jars to Maven Central.

Release process

The majority of the release procedure is executed by the publish.yml workflow. It is kicked off by a push to a branch name that matches release/v*. Please familiarize yourself with the steps in that workflow.

0. Poll Deephaven CSV team

Ensure you are proceeding with a known release, and there aren't any blockers.

1. Repository prerequisites

These release notes assume that the Deephaven CSV repository git@github.com:deephaven/deephaven-csv.git is referenced as the remote named upstream. Please ensure your local repository is set up as such, or that you replace any commands with the appropriately named remote:

$ git remote get-url upstream
git@github.com:deephaven/deephaven-csv.git

2. Create release branch and commit version bump

Ensure you are up-to-date with upstream/main, or at the commit that you want to start a new release from. If you are unsure what commit to start from, please ask. Most of the time, the main branch will be referencing a -SNAPSHOT version, and we'll want to update this to a non-snapshot version. Please double-check you are on the version you expect to be releasing. The releases have so far proceeded with branches named release/vX.Y.Z, where X.Y.Z is the version number (this isn't a technical requirement), please replace X.Y.Z with the appropriate version.

$ git fetch upstream
$ git checkout upstream/main
$ git checkout -b release/vX.Y.Z
$ # edit gradle.properties, remove -SNAPSHOT
$ git add gradle.properties
# Do a find and replace for old version, replace with new version
(across READMEs)
</tr></table>

... (truncated)

Commits

Updates `io.deephaven:deephaven-csv-fast-double-parser` from 0.12.0 to 0.14.0
Release notes

Sourced from io.deephaven:deephaven-csv-fast-double-parser's releases.

v0.14.0

What's Changed

Full Changelog: https://github.com/deephaven/deephaven-csv/compare/v0.13.0...v0.14.0

v0.13.0

What's Changed

Full Changelog: https://github.com/deephaven/deephaven-csv/compare/v0.12.0...v0.13.0

Changelog

Sourced from io.deephaven:deephaven-csv-fast-double-parser's changelog.

Release

This document is primarily targeted towards Deephaven CSV release managers. It is meant to contain the necessary instructions for executing a Deephaven CSV release.

Please be sure to read and understand this document in full before proceeding with a release. If you have any questions or concerns about any of the commands, please reach out.

Jar artifacts

The deephaven-csv release process consists of releasing two jars to Maven Central.

Release process

The majority of the release procedure is executed by the publish.yml workflow. It is kicked off by a push to a branch name that matches release/v*. Please familiarize yourself with the steps in that workflow.

0. Poll Deephaven CSV team

Ensure you are proceeding with a known release, and there aren't any blockers.

1. Repository prerequisites

These release notes assume that the Deephaven CSV repository git@github.com:deephaven/deephaven-csv.git is referenced as the remote named upstream. Please ensure your local repository is set up as such, or that you replace any commands with the appropriately named remote:

$ git remote get-url upstream
git@github.com:deephaven/deephaven-csv.git

2. Create release branch and commit version bump

Ensure you are up-to-date with upstream/main, or at the commit that you want to start a new release from. If you are unsure what commit to start from, please ask. Most of the time, the main branch will be referencing a -SNAPSHOT version, and we'll want to update this to a non-snapshot version. Please double-check you are on the version you expect to be releasing. The releases have so far proceeded with branches named release/vX.Y.Z, where X.Y.Z is the version number (this isn't a technical requirement), please replace X.Y.Z with the appropriate version.

$ git fetch upstream
$ git checkout upstream/main
$ git checkout -b release/vX.Y.Z
$ # edit gradle.properties, remove -SNAPSHOT
$ git add gradle.properties
# Do a find and replace for old version, replace with new version
(across READMEs)
</tr></table>

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) ---
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- gradle/libs.versions.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gradle/libs.versions.toml b/gradle/libs.versions.toml index 2fd2a0ebe64..0a130cb8481 100644 --- a/gradle/libs.versions.toml +++ b/gradle/libs.versions.toml @@ -18,7 +18,7 @@ confluent = "7.6.0" confluent-kafka-clients = "7.6.0-ccs" dagger = "2.44" deephaven-barrage = "0.6.0" -deephaven-csv = "0.12.0" +deephaven-csv = "0.14.0" deephaven-hash = "0.1.0" deephaven-suan-shu = "0.1.0" dev-dirs = "26"