Skip to content

Conversation

@cdcabrera
Copy link
Member

Description

Corrects current build fail due to incorrect "-eng" repo version... switches back from an exact NPM package version to a ">=" version.

PR Checklist

  • [n/a] Unit tests are included
  • [n/a] Screenshots are attached (if there are visual changes in the UI)
  • [n/a] A Designer is assigned as a reviewer (if there are visual changes in the UI)
  • [n/a] A CSS rep is assigned as a reviewer (if there are visual changes in the UI)

Copy link
Member

@dtaylor113 dtaylor113 left a comment

Choose a reason for hiding this comment

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

What happened? We changed this previously in https://github.com/patternfly/angular-patternfly/pull/553/files

@cdcabrera
Copy link
Member Author

Dunno, I remember it but now the change just isn't there

@jeff-phillips-18
Copy link
Member

It got updated by patternfly-build. Will this re-occur?

@cdcabrera
Copy link
Member Author

cdcabrera commented Aug 8, 2017

per @jeff-phillips-18

git blame... 4ccc15b
Will this re-occur?

Indeed, this will probably happen again since the release scripts are trying to increment the version and we're customizing it... might need an exception where if it sees anything in addition to version number it ignores it.

That being said this may be a non-issue by incrementing to the latest version, with little bit more testing.

Based on everything this PR, as is, provides an immediate fix, not something long-term.

@cdcabrera cdcabrera changed the title Restores Build Package Update from Release [WIP] Restores Build Package Update from Release Aug 8, 2017
-eng repo version
@cdcabrera cdcabrera force-pushed the build-packageupdate branch from 28a8d74 to e45b940 Compare August 8, 2017 18:06
@cdcabrera cdcabrera changed the title [WIP] Restores Build Package Update from Release Restores Build Package Update from Release Aug 8, 2017
@jeff-phillips-18 jeff-phillips-18 merged commit da3f15e into patternfly:master Aug 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants