Skip to content

Reversionning azure-core to b5 for CI clarity#8083

Merged
lmazuel merged 1 commit into
masterfrom
core_b5
Oct 21, 2019
Merged

Reversionning azure-core to b5 for CI clarity#8083
lmazuel merged 1 commit into
masterfrom
core_b5

Conversation

@lmazuel

@lmazuel lmazuel commented Oct 21, 2019

Copy link
Copy Markdown
Member

No description provided.

@lmazuel lmazuel added Client This issue points to a problem in the data-plane of the library. Azure.Core blocking-release Blocks release labels Oct 21, 2019
@AutorestCI

AutorestCI commented Oct 21, 2019

Copy link
Copy Markdown
Contributor

(message created by the CI based on PR content)

Installation instruction

Package azure-core

You can install the package azure-core of this PR using the following command:
pip install "git+https://github.com/Azure/azure-sdk-for-python@core_b5#egg=azure-core&subdirectory=azure-core"

You can build a wheel to distribute for test using the following command:
pip wheel --no-deps "git+https://github.com/Azure/azure-sdk-for-python@core_b5#egg=azure-core&subdirectory=azure-core"

If you have a local clone of this repository, you can also do:

  • git checkout core_b5
  • pip install -e ./azure-core

Or build a wheel file to distribute for testing:

  • git checkout core_b5
  • pip wheel --no-deps ./azure-core

Direct download

Your files can be directly downloaded here:

# --------------------------------------------------------------------------

VERSION = "1.0.0b4"
VERSION = "1.0.0b5"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1.0.0

@lmazuel
lmazuel merged commit a798379 into master Oct 21, 2019
@lmazuel
lmazuel deleted the core_b5 branch October 21, 2019 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Azure.Core blocking-release Blocks release Client This issue points to a problem in the data-plane of the library.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants