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

[NewRelease] v0.27.1 #218

Merged
merged 2 commits into from
Apr 3, 2020
Merged

[NewRelease] v0.27.1 #218

merged 2 commits into from
Apr 3, 2020

Conversation

lillchan
Copy link
Collaborator

@lillchan lillchan commented Apr 3, 2020

What problem does this Pull Request solve?

Release new version 0.27.1 with bug fix #216

If you don't have an issue created, please create the issue first describing the problem and then open the PR

Type of change

What type of change does your code introduce to the provider? Please put an x (w/o heading/trailing white spaces) in the boxes that apply:

  • New feature (change that adds new functionality)
  • Bug-fix (change that fixes current functionality)
  • Tech debt (enhances the current functionality)
  • New release (pumps the version)

Checklist

Please put an x (w/o heading/trailing white spaces) in the boxes that apply:

  • I have read and followed the CONTRIBUTING guidelines
  • I have added tests that prove my fix is effective or that my feature works
  • I have made sure code compiles correctly and all tests are passing by running make test-all
  • I have added/updated necessary documentation (if appropriate)
  • I have added the following info to the title of the PR (pick the appropriate option for the type of change). This is important because the release notes will include this information.
    • Feature Request: PRs related to feature requests should have in the title [FeatureRequest: Issue #X] <PR Title>
    • Bug Fixes: PRs related to bug fixes should have in the title [BugFix: Issue #X] <PR Title>
    • Tech Debt: PRs related to technical debt should have in the title [TechDebt: Issue #X] <PR Title>
    • New Release: PRs related to a new release should have in the title [NewRelease] vX.Y.Z

Checklist for Admins

  • Label is populated
  • PR is assigned to the corresponding project
  • PR has at least 1 reviewer and 1 assignee

@lillchan lillchan requested a review from dikhan April 3, 2020 00:48
@lillchan lillchan self-assigned this Apr 3, 2020
@lillchan lillchan added this to Backlog in API Terraform Provider (OpenAPI 2.0) via automation Apr 3, 2020
API Terraform Provider (OpenAPI 2.0) automation moved this from Backlog to In progress Apr 3, 2020
@codecov
Copy link

codecov bot commented Apr 3, 2020

Codecov Report

Merging #218 into master will not change coverage by %.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #218   +/-   ##
=======================================
  Coverage   90.27%   90.27%           
=======================================
  Files          55       55           
  Lines        3219     3219           
=======================================
  Hits         2906     2906           
  Misses        208      208           
  Partials      105      105           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5c2c992...81117e2. Read the comment docs.

@dikhan dikhan merged commit 00f4074 into master Apr 3, 2020
API Terraform Provider (OpenAPI 2.0) automation moved this from In progress to Done Apr 3, 2020
@dikhan dikhan deleted the version/update-to-0.27.1 branch April 3, 2020 00:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

2 participants