Skip to content
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.

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

Cargo.toml: Update version to 1.0.1 #31

Merged
merged 2 commits into from
Sep 24, 2024
Merged

Conversation

makubacki
Copy link
Member

Description

Updates the crate version in anticipation of a v1.0 tagged release.

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

How This Was Tested

  • N/A

Integration Instructions

  • N/A

Updates the crate version in anticipation of
a v1.0 tagged release.

Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
@makubacki makubacki added the semver:patch Pull requests that should increment the release patch version label Sep 24, 2024
@makubacki makubacki requested review from os-d and vineelko September 24, 2024 14:10
@makubacki makubacki self-assigned this Sep 24, 2024
@github-actions github-actions bot added the impact:non-functional Does not have a functional impact label Sep 24, 2024
@makubacki makubacki enabled auto-merge (squash) September 24, 2024 16:21
@makubacki makubacki disabled auto-merge September 24, 2024 16:21
@makubacki makubacki changed the title Cargo.toml: Update version to 1.0 Cargo.toml: Update version to 1.0.1 Sep 24, 2024
@makubacki makubacki enabled auto-merge (squash) September 24, 2024 16:24
@makubacki makubacki requested a review from apop5 September 24, 2024 16:25
@makubacki makubacki merged commit 2f259c8 into microsoft:main Sep 24, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact:non-functional Does not have a functional impact semver:patch Pull requests that should increment the release patch version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants