Closed clintoncwolfe closed 5 years ago
We have a report that v 1.1.1 and 1.2.0 were not automatically published to rubygems. Do a dummy merge and verify that publishing works.
[Version of the project installed]
[Details about the environment such as the Operating System, cookbook details, etc...]
[What you are trying to achieve and you can't?]
[If you are filing an issue what are the things we need to do in order to repro your problem?]
[What are you expecting to happen as the consequence of above reproduction steps?]
[What actually happens after the reproduction steps?]
Turns out everything works fine; we simply did not issue a promote command. v1.2.0 has now been promoted to rubygems. Attn @russellseymour
Version:
We have a report that v 1.1.1 and 1.2.0 were not automatically published to rubygems. Do a dummy merge and verify that publishing works.
[Version of the project installed]
Environment:
[Details about the environment such as the Operating System, cookbook details, etc...]
Scenario:
[What you are trying to achieve and you can't?]
Steps to Reproduce:
[If you are filing an issue what are the things we need to do in order to repro your problem?]
Expected Result:
[What are you expecting to happen as the consequence of above reproduction steps?]
Actual Result:
[What actually happens after the reproduction steps?]