Skip to content

Make older release pages durable using tags and SHAs that won't break if main changes #10375

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.

Sign up for GitHub

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

Draft
Alan Zimmer (alzimmermsft) wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Make older release pages durable using tags and SHAs that won't break if main changes #10375

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
38 changes: 38 additions & 0 deletions _data/releases/2019-07-10/dotnet.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
content: |2

The Azure SDK team is pleased to announce our July 2019 client library preview. This represents the first release of a ground-up rewrite of our client libraries to ensure consistency, idiomatic design, productivity, and an excellent developer experience. This preview includes new libraries for Storage (Blobs, Queues, and Files), Key Vault (Secrets and Keys), Event Hubs, Cosmos, and Identity.

## Installation Instructions

To install any of our packages, please search for them via `Manage NuGet Packages...` in Visual Studio (with `Include prerelease` checked) or copy these commands into your terminal:

$> dotnet add package Azure.Storage.Blobs --version 12.0.0-preview.1
$> dotnet add package Azure.Storage.Queues --version 12.0.0-preview.1
$> dotnet add package Azure.Storage.Files --version 12.0.0-preview.1

$> dotnet add package Azure.Security.KeyVault.Secrets --version 4.0.0-preview.1
$> dotnet add package Azure.Security.KeyVault.Keys --version 4.0.0-preview.1

$> dotnet add package Azure.Messaging.EventHubs --version 5.0.0-preview.1

$> dotnet add package Microsoft.Azure.Cosmos --version 3.0.0.19-preview

$> dotnet add package Azure.Identity --version 1.0.0-preview.2

## Feedback

If you have a bug or feature request for one of the libraries, please [file an issue in our repo](https://github.com/Azure/azure-sdk-for-net/issues/new/choose).

## Changelog

Detailed changelogs are linked from the [Quick Links](#quick-links) below. Here are some of the highlights:

- New client libraries were created using the [Azure SDK Design Guidelines for .NET][dotnet-guidelines] resulting in consistent API patterns and shared features like automatic retries, authentication, logging, configurable transport pipelines, exceptions, mocking, etc.
- Support for Azure Active Directory credentials using our new Identity library that embrace the future of authentication across Azure services.
- Parity across synchronous and asynchronous APIs offering a choice appropriate to your application.

## Quick Links

See [Nov Release](%%SITE_BASEURL%%/releases/2019-11/dotnet.html)

%%RELEASE_REFERENCES%%
75 changes: 75 additions & 0 deletions _data/releases/2019-07-10/java.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,75 @@
content: |2

The Azure SDK team is pleased to make available the July 2019 client library preview release. This represents the first release of the ground-up rewrite of the client libraries to ensure consistency, idiomatic design, and excellent developer experience and productivity. This preview release includes new client libraries for Azure App Configuration, Cosmos, Identity, Key Vault (keys and secrets), Event Hubs, and Storage (blob).

## Installation Instructions

To use the preview libraries, refer to the Maven dependency information below, which may be copied into your projects Maven pom.xml file as appropriate. If you are using a different build tool, refer to its documentation on how to specify dependencies.

```xml
<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-data-appconfiguration</artifactId>
<version>1.0.0-preview.1</version>
</dependency>

<dependency>
<groupId>com.microsoft.azure</groupId>
<artifactId>azure-cosmos</artifactId>
<version>3.0.0</version>
</dependency>

<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-identity</artifactId>
<version>1.0.0-preview.1</version>
</dependency>

<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-keyvault-keys</artifactId>
<version>4.0.0-preview.1</version>
</dependency>

<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-keyvault-secrets</artifactId>
<version>4.0.0-preview.1</version>
</dependency>

<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-messaging-eventhubs</artifactId>
<version>5.0.0-preview.1</version>
</dependency>

<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-storage-blob</artifactId>
<version>12.0.0-preview.1</version>
</dependency>
```

## Feedback
If you have a bug or feature request for one of the libraries, please post an issue to [GitHub](https://github.com/azure/azure-sdk-for-java/issues).

## Changelog
Detailed change logs are linked to in the Quick Links below. Here are some critical call outs.

* Designed based on the [Azure SDK Design Guidelines for Java][java-guidelines], resulting in a consistent API design and common feature set such as HTTP retries, logging, transport protocols, authentication protocols, etc.
* Modernized API making use of Java 8 features such as streams, new date / time, functional interfaces, etc, to offer an improved and more productive developer experience.
* Synchronous and asynchronous APIs offer developers simplicity for simple cases, and full asynchronousity when performance and scalability matters. Reactive streams are offered using [Project Reactor](https://projectreactor.io).

## Need help?
* For reference documentation visit the [Azure SDK for Java documentation](https://azure.github.io/azure-sdk-for-java/).
* For tutorials, samples, quick starts and other documentation, visit [Azure for Java Developers](https://docs.microsoft.com/java/azure/).
* For build reports on code quality, test coverage, etc, visit [Azure Java SDK](https://azuresdkartifacts.blob.core.windows.net/azure-sdk-for-java/index.html).
* File an issue via [Github Issues](https://github.com/Azure/azure-sdk-for-java/issues/new/choose).
* Check [previous questions](https://stackoverflow.com/questions/tagged/azure-java-sdk) or ask new ones on StackOverflow using `azure-java-sdk` tag.

## Quick Links

See [Nov Release](%%SITE_BASEURL%%/releases/2019-11/java.html)


%%RELEASE_REFERENCES%%
31 changes: 31 additions & 0 deletions _data/releases/2019-07-10/js.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
content: |2

The Azure SDK team is pleased to make available the July 2019 client library preview release. This represents the first release of the ground-up rewrite of the client libraries to ensure consistency, idiomatic design, and excellent developer experience and productivity. This preview release includes new client libraries for Key Vault (keys and secrets), Event Hubs, Storage (blob, files and queues) and Cosmos.

## Installation Instructions

To install the packages, copy and paste the below into a terminal.

$> npm install @azure/keyvault-keys@4.0.0-preview.2
$> npm install @azure/keyvault-secrets@4.0.0-preview.2
$> npm install @azure/storage-queue@12.0.0-preview.1
$> npm install @azure/storage-file@12.0.0-preview.1
$> npm install @azure/storage-blob@12.0.0-preview.1
$> npm install @azure/event-hubs@5.0.0-preview.1
$> npm install @azure/cosmos@next

## Feedback
If you have a bug or feature request for one of the libraries, please post an issue at the [azure-sdk-for-js repository](https://github.com/azure/azure-sdk-for-js/issues)

## Changelog
Detailed change logs are linked to in the Quick Links below. Here are some critical call outs.

- Designed based on the [Azure SDK Design Guidelines for Typescript][typescript-guidelines], resulting in a consistent API design and common feature set such as HTTP retries, logging, transport protocols, authentication protocols, cancellation mechanisms etc.
- Support for Azure Active Directory credentials created using the new [@azure/identity](https://www.npmjs.com/package/@azure/identity) library. Moving forward, this would be the common mode of authentication for all Azure SDK libraries.
- Modernized API making use of async functions and async iterators, to offer an improved and more productive developer experience.

## Quick Links

See [Nov Release](%%SITE_BASEURL%%/releases/2019-11/js.html)

%%RELEASE_REFERENCES%%
90 changes: 90 additions & 0 deletions _data/releases/2019-07-10/python.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,90 @@
content: |2

The Azure SDK team is pleased to make available the July 2019 client library preview release. This represents the first release of the ground-up rewrite of the client libraries to ensure consistency, idiomatic design, and excellent developer experience and productivity. This preview release includes new client libraries for Azure Cosmos, Identity, Key Vault (keys and secrets), Event Hubs, and Storage (blob, files and queues).

## Installation Instructions

To install the latest preview version of the packages, copy and paste the following commands into a terminal:

```bash
pip install --pre azure-cosmos
pip install --pre azure-eventhub
pip install --pre azure-identity
pip install --pre azure-keyvault-keys
pip install --pre azure-keyvault-secrets
pip install --pre azure-storage-blob
pip install --pre azure-storage-file
pip install --pre azure-storage-queue
```

## Feedback

If you have a bug or feature request for one of the libraries, please post an issue to [GitHub](https://github.com/azure/azure-sdk-for-python/issues).

## Changelog

Detailed change logs are linked to in the Quick Links below. Here are some critical call outs.

### Identity

* The new `azure-identity` package simplifies authentication across the Azure Python libraries. It supports token authentication using an Azure Active Directory service principal or [managed identity](https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview). Additional forms of authentication (e.g. user authentication) will be added shortly.

### Cosmos

* New clients corresponding to each level in the object hierarchy (account, container, database etc.) have been created. You can directly access child clients by name.

### Keyvault

* The `azure-keyvault` package has been split into `azure-keyvault-keys` and `azure-keyvault-secrets`. We intend to add `azure-keyvault-certificates` shortly.

*Note: The `azure-keyvault-keys` and `azure-keyvault-secrets` packages cannot be installed into the same environment as the existing `azure-keyvault` package.*

#### Keys

* A new `azure.keyvault.keys.KeyClient` type is introduced.
* Client instances are scoped to vaults (an instance interacts with one vault only)
* Asynchronous API supported on Python 3.5.3+

#### Secrets

* A new `azure.keyvault.secrets.SecretClient` type is introduced.
* Client instances are scoped to vaults (an instance interacts with one vault only)
* Asynchronous API supported on Python 3.5.3+

### Storage

#### Blobs

New API design with separate clients for operations on the account, containers and blobs:

* `BlobServiceClient`: This client handles account-level operations. This includes managing service properties and listing the containers within an account.
* `ContainerClient`: The client handles operations for a particular container. This includes creating or deleting that container, as well as listing the blobs within that container and managing properties and metadata.
* `BlobClient`: The client handles operations for a particular blob. This includes creating or deleting that blob, as well as upload and download data and managing properties. This BlobClient handles all blob types (block, page and append). Where operations can behave differently according to type (i.e. upload_blob) the default behaviour will be block blobs unless otherwise specified.
* `LeaseClient`: Handles all lease operations for both containers and blobs.
These clients can be accessed by navigating down the client hierarchy, or instantiated directly using URLs to the resource (account, container or blob). For full details on the new API, please see the reference documentation.

#### Files

New API design with separate clients for operations on the account, files, shares and directories:

* `FileServiceClient`: This client handles account-level operations. This includes managing service properties and listing the shares within an account.
* `ShareClient`: The client handles operations for a particular share. This includes creating or deleting that share, as well as listing the directories within that share, and managing properties and metadata.
* `DirectoryClient`: The client handles operations for a particular directory. This includes creating or deleting that directory, as well as listing the files and subdirectories, and managing properties and metadata.
* `FileClient`: The client handles operations for a particular file. This includes creating or deleting that file, as well as upload and download data and managing properties.

These clients can be accessed by navigating down the client hierarchy, or instantiated directly using URLs to the resource (account, share, directory or file). For full details on the new API, please see the reference documentation.

#### Queues

New API design with separate clients for operations on the account and individual queues:

* `QueueServiceClient`: This client handles account-level operations. This includes managing service properties and listing the queues within an account.
* `QueueClient`: The client handles operations within a particular queue. This includes creating or deleting that queue, as well as enqueueing and dequeueing messages.

These clients can be accessed by navigating down the client hierarchy, or instantiated directly using URLs to the resource (account or queue). For full details on the new API, please see the reference documentation.

## Quick Links

See [Nov Release](%%SITE_BASEURL%%/releases/2019-11/python.html)

%%RELEASE_REFERENCES%%
52 changes: 52 additions & 0 deletions _data/releases/2019-08-06/dotnet.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
content: |2-

The Azure SDK team is pleased to announce our August 2019 client library preview. This represents the first release of a ground-up rewrite of our client libraries to ensure consistency, idiomatic design, productivity, and an excellent developer experience. This preview includes new libraries for Storage (Blobs, Queues, and Files), Key Vault (Secrets and Keys), Event Hubs, Cosmos, and Identity.

## Installation Instructions

To install any of our packages, please search for them via `Manage NuGet Packages...` in Visual Studio (with `Include prerelease` checked) or copy these commands into your terminal:

$> dotnet add package Azure.Storage.Blobs --version 12.0.0-preview.2
$> dotnet add package Azure.Storage.Queues --version 12.0.0-preview.2
$> dotnet add package Azure.Storage.Files --version 12.0.0-preview.2

$> dotnet add package Azure.Security.KeyVault.Secrets --version 4.0.0-preview.3
$> dotnet add package Azure.Security.KeyVault.Keys --version 4.0.0-preview.2

$> dotnet add package Azure.Messaging.EventHubs --version 5.0.0-preview.2

$> dotnet add package Azure.Identity --version 1.0.0-preview.3

## Feedback

If you have a bug or feature request for one of the libraries, please [file an issue in our repo](https://github.com/Azure/azure-sdk-for-net/issues/new/choose).

## Changelog

Detailed changelogs are linked from the [Quick Links](#quick-links) below. Here are some of the highlights:

- New client libraries were created using the [Azure SDK Design Guidelines for .NET][dotnet-guidelines] resulting in consistent API patterns and shared features like automatic retries, authentication, logging, configurable transport pipelines, exceptions, mocking, etc.
- Support for Azure Active Directory credentials using our new Identity library that embrace the future of authentication across Azure services.
- Parity across synchronous and asynchronous APIs offering a choice appropriate to your application.
- Updated dependencies on the latest (preview-7) version of `Azure.Core` library.

### Azure Identity

- Added new user credential types, allowing authentication within client applications.

### Event Hubs

- Expanded support for sending multiple messages in a single call by adding the ability to create a batch which avoids the error scenario of exceeding size limits. Users having bandwidth concerns can control the batch size as desired.
- Introduced a new model for consuming events via the `EventProcessor` class. This simplifies the process of checkpointing today and will handle load balancing across partitions in upcoming updates.
- Enabled the ability to subscribe to the events exposed by an `EventHubConsumer` in the form of an asynchronous iterator. With the iterator, consumers are able to use the familiar `foreach` pattern to receive events as they are available and to process them.

### Key Vault

- Added support for cryptographic operations (such as sign, verify, encrypt, and decrypt) using KeyVault keys.
- Added support for challenge based authentication.

## Quick Links

See [Nov Release](%%SITE_BASEURL%%/releases/2019-11/dotnet.html)

%%RELEASE_REFERENCES%%
Loading
Loading