v0.0.59

Make rapids-twine look like rapids-twine-new (#63)

We know the `-new` version also works, so to minimize disruptions with
existing workflows it'll be easiest to just modify the original script
then eventually remove the `-new` version once nothing is using the
legacy workflows that call it.

Part of #54

v0.0.58

Fix prompts for running a nightly build/test locally (#62)

RAPIDS CI supports running CI builds locally using the instructions
here: https://docs.rapids.ai/resources/reproducing-ci/
When a build step requires downloading from S3, the tools script will
prompt for the needed environment variable settings.
```
export RAPIDS_BUILD_TYPE=pull-request # or "branch" or "nightly"
export RAPIDS_REPOSITORY=rapidsai/cugraph
export RAPIDS_REF_NAME=pull-request/3258 # or "branch-YY.MM" for "branch"/"nightly" builds
```

The steps for reproducing a `nightly` test were not working and produced
the following result.

```
[rapids-download-conda-from-s3] Local run detected.
[rapids-download-conda-from-s3] NVIDIA VPN connectivity is required to download workflow artifacts.

Enter workflow type (one of: pull-request|branch|nightly): nightly

Suppress this prompt in the future by setting the 'RAPIDS_BUILD_TYPE' environment variable:
export RAPIDS_BUILD_TYPE=nightly


Enter org/repository name (e.g. rapidsai/cudf): rapidsai/cudf

Suppress this prompt in the future by setting the 'RAPIDS_REPOSITORY' environment variable:
export RAPIDS_REPOSITORY=rapidsai/cudf


Enter pull-request number (e.g. 1546): branch-23.08

Suppress this prompt in the future by setting the 'RAPIDS_REF_NAME' environment variable:
export RAPIDS_REF_NAME=pull-request/branch-23.08


Using HEAD commit for artifact commit hash. Overwrite this by setting the 'RAPIDS_SHA' environment variable:
export RAPIDS_SHA=1854ac86d08e545376704959436ec370bdd8117a

/usr/local/bin/rapids-s3-path: line 40: RAPIDS_NIGHTLY_DATE: unbound variable

```
The nightly build requires the `RAPIDS_NIGHTLY_DATE` date in
`YYYY-MM-DD` format and the `RAPIDS_REF_NAME` is expected to be the
branch name.

This PR updates the prompt logic to allow running a nightly build
locally.

v0.0.57

Make `rapids-get-artifact` work locally (#59)

This PR ensures that `rapids-get-artifact` works locally.

This request was made by @bdice who was attempting to use the script
locally to debug some CUDA 12 issues.

I've moved the logic for downloading, extracting, and printing the
artifact's path to a new script, `_rapids-download-from-s3`.

This script is then called by both `rapids-download-from-s3` and
`rapids-get-artifact`.

In the future, I would like to rework some of the scripts regarding
artifact uploading/downloading, but I think we need to finish reworking
the wheel workflows before that will be feasible.

v0.0.56

Add message about viewing docs locally to `rapids-upload-docs` (#58)

As noted in https://github.com/rapidsai/rmm/pull/1288, the value of
`RAPIDS_DOCS_DIR` is random and generated by `mktemp -d`.

Therefore, it will be useful to print out this directory for users who
are doing local builds according to the repro instructions here:
https://docs.rapids.ai/resources/reproducing-ci/.

Additionally, a `python -m http.server` command is printed so that users
can view the built docs in their browser.

v0.0.55

Add `rapids-upload-docs` script (#56)

## Summary

This PR adds a new script, `rapids-upload-docs`.

The purpose of this script is to consolidate the logic for uploading
documentation to S3.

This will be useful for the upcoming two efforts:

- enabling documentation files to be previewed on PRs
- temporarily halting documentation uploads to the `rapidsai-docs`
bucket while we restructure the bucket in anticipation of some upcoming
website changes


## Usage

The snippet below shows how the script can be used.

It requires two environment variables be set:

- `RAPIDS_VERSION_NUMBER` - a RAPIDS version (e.g. `23.06`)
- `RAPIDS_DOCS_DIR` - a path to a directory containing the docs to
upload (see folder structure below)


```sh
export RAPIDS_VERSION_NUMBER="23.06"
export RAPIDS_DOCS_DIR=${RAPIDS_DOCS_DIR:-"${PWD}/documentation"}

rapids-logger "Build cuDF Sphinx docs"
pushd docs/cudf
sphinx-build -b dirhtml source _html
sphinx-build -b text source _text
mkdir -p "${RAPIDS_DOCS_DIR}/cudf/{html,txt}"
mv _html/* "${RAPIDS_DOCS_DIR}/cudf/html"
mv _text/* "${RAPIDS_DOCS_DIR}/cudf/txt"
popd

rapids-logger "Build dask-cuDF Sphinx docs"
pushd docs/dask_cudf
sphinx-build -b dirhtml source _html
sphinx-build -b text source _text
mkdir -p "${RAPIDS_DOCS_DIR}/dask-cudf/{html,txt}"
mv _html/* "${RAPIDS_DOCS_DIR}/dask-cudf/html"
mv _text/* "${RAPIDS_DOCS_DIR}/dask-cudf/txt"
popd

rapids-upload-docs
```

The structure of `RAPIDS_DOCS_DIR` should look like this:

```
$RAPIDS_DOCS_DIR
├── cudf
│   ├── html
│   │   └── <html files>
│   └── txt
│       └── <txt files>
└── dask-cudf
    ├── html
    │   └── <html files>
    └── txt
        └── <txt files>
```

v0.0.54

wheel-ctk-name-gen (#55)

Part of https://github.com/rapidsai/shared-action-workflows/issues/77

---------

Co-authored-by: Vyas Ramasubramani <[email protected]>

v0.0.53

Update `RAPIDS_DATE_STRING` (#53)

This PR updates how `RAPIDS_DATE_STRING` is computed.

The variable's value is now computed from the workflow run date.

This will help ensure that RAPIDS packages are published on a nightly
basis even if no changes to the source code have been made.

v0.0.52

Use more robust method to launch twine (#52)

Using the twine executable directly relies on the Python bin directory
being added to the path, which is not reliably the case in different
environments. I've created a new copy of the script since I'm iterating
very actively right now in the new wheels workflow. We can get rid of
the old script once I've verified that everything is working as
expected.

v0.0.51

Add scripts for assembling docker multiarch manifests from a local re…

v0.0.50

Remove rapids-get-rapids-version-from-git (#50)

This tool is not used anymore

Signed-off-by: Jordan Jacobelli <[email protected]>