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

Update expeditor config to publish rubygems on promote #11

Merged
merged 1 commit into from
Aug 7, 2019

Conversation

clintoncwolfe
Copy link
Contributor

@clintoncwolfe clintoncwolfe commented Aug 7, 2019

Signed-off-by: Clinton Wolfe [email protected]

Description

Looks like the expeditor config was missing a promote section entirely.
I'm leaving this set to include a patch version bump so we'll get a new (but pointless) build so we'll have something to promote.

Related Issue

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New content (non-breaking change)
  • Breaking change (a content change which would break existing functionality or processes)

Checklist:

  • I have read the CONTRIBUTING document.

@clintoncwolfe clintoncwolfe force-pushed the cw/expeditor-promote-gem branch 2 times, most recently from 7564bce to 804cd91 Compare August 7, 2019 16:20
@clintoncwolfe clintoncwolfe added the Type: Enhancement Improves an existing feature label Aug 7, 2019
@clintoncwolfe clintoncwolfe requested review from miah and tduffield August 7, 2019 16:23
@clintoncwolfe clintoncwolfe force-pushed the cw/expeditor-promote-gem branch from 804cd91 to 0af41a6 Compare August 7, 2019 20:28
@clintoncwolfe clintoncwolfe force-pushed the cw/expeditor-promote-gem branch from 0af41a6 to 8bd4876 Compare August 7, 2019 21:13
@clintoncwolfe clintoncwolfe merged commit 1474305 into master Aug 7, 2019
@clintoncwolfe clintoncwolfe deleted the cw/expeditor-promote-gem branch August 7, 2019 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Aspect: Packaging Type: Enhancement Improves an existing feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants