- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 30 for releases (0.49 sec)
-
README.md
# Guava: Google Core Libraries for Java [![Latest release](https://img.shields.io/github/release/google/guava.svg)](https://github.com/google/guava/releases/latest) [![Build Status](https://github.com/google/guava/workflows/CI/badge.svg?branch=master)](https://github.com/google/guava/actions) [![OpenSSF Best Practices](https://bestpractices.coreinfrastructure.org/projects/7197/badge)](https://bestpractices.coreinfrastructure.org/projects/7197)
Plain Text - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Wed May 01 18:44:57 GMT 2024 - 5.9K bytes - Viewed (0) -
README.md
``` The OkHttp `3.12.x` branch supports Android 2.3+ (API level 9+) and Java 7+. These platforms lack support for TLS 1.2 and should not be used. Releases -------- Our [change log][changelog] has release history. The latest release is available on [Maven Central](https://search.maven.org/artifact/com.squareup.okhttp3/okhttp/4.12.0/jar). ```kotlin implementation("com.squareup.okhttp3:okhttp:4.12.0") ```
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Wed Dec 20 23:27:07 GMT 2023 - 6.2K bytes - Viewed (0) -
docs/bucket/replication/README.md
> NOTE: If you are using a mc version below `RELEASE.2022-12-24T15-21-38Z`, the --remote-bucket flag needs an ARN generated by `mc admin bucket remote add` command. For mc versions RELEASE.2021-09-02T09-21-27Z and older, the remote target ARN needs to be passed in the --arn flag and actual remote bucket name in --remote-bucket flag of `mc replicate add`. For example, in older releases of mc replication configuration used to be added with: ```
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Jan 24 23:46:33 GMT 2023 - 18.2K bytes - Viewed (0) -
docs/bucket/notifications/README.md
> database (string) database name (used only if `connection_string` is empty) > ``` > > These are now deprecated, if you plan to upgrade to any releases after _RELEASE.2020-04-10T03-34-42Z_ make sure > to migrate to only using _connection_string_ option. To migrate, once you have upgraded all the servers use the > following command to update the existing notification targets. >
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 84K bytes - Viewed (2) -
README.md
Questions related to the usage of Maven should be posted on the [Maven User List][users-list]. Where can I get the latest release? ----------------------------------- You can download the release source from our [download page][maven-download]. Contributing ------------ If you are interested in the development of Maven, please consult the
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sun Mar 03 21:28:30 GMT 2024 - 4.3K bytes - Viewed (0) -
README.md
## Contributors [Thank you](https://github.com/go-gorm/gorm/graphs/contributors) for contributing to the GORM framework! ## License © Jinzhu, 2013~time.Now
Plain Text - Registered: Sun May 05 09:35:13 GMT 2024 - Last Modified: Tue Nov 07 02:20:06 GMT 2023 - 1.8K bytes - Viewed (0) -
docs/chroot/README.md
- Chroot installed on your machine. ## 2. Install MinIO in Chroot ```sh mkdir -p /mnt/export/${USER}/bin wget https://dl.min.io/server/minio/release/linux-amd64/minio -O /mnt/export/${USER}/bin/minio chmod +x /mnt/export/${USER}/bin/minio ``` Bind your `proc` mount to the target chroot directory ``` sudo mount --bind /proc /mnt/export/${USER}/proc ```
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 1.7K bytes - Viewed (0) -
helm/minio/README.md
You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ```
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Jan 24 07:27:57 GMT 2024 - 10.9K bytes - Viewed (0) -
manifests/charts/gateway/README.md
The script below can handle this for you. Replace `RELEASE` and `NAMESPACE` with the name and namespace of the release: ```console KINDS=(service deployment) RELEASE=istio-ingressgateway NAMESPACE=istio-system for KIND in "${KINDS[@]}"; do kubectl --namespace $NAMESPACE --overwrite=true annotate $KIND $RELEASE meta.helm.sh/release-name=$RELEASE
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 19:38:07 GMT 2024 - 6.6K bytes - Viewed (0) -
doc/README.md
## For the release team At the start of a release development cycle, the contents of `next` should be deleted and replaced with those of `initial`. From the repo root: > cd doc > rm -r next/* > cp -r initial/* next Then edit `next/1-intro.md` to refer to the next version. To prepare the release notes for a release, run `golang.org/x/build/cmd/relnote generate`.
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Fri Apr 26 21:24:36 GMT 2024 - 1.9K bytes - Viewed (0)