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

FYI: I unpublished 4.0.0 #50

Closed
stefanpenner opened this issue Feb 21, 2019 · 10 comments
Closed

FYI: I unpublished 4.0.0 #50

stefanpenner opened this issue Feb 21, 2019 · 10 comments

Comments

@stefanpenner
Copy link
Contributor

FYI: I unpublished 4.0.0 per @Turbo87's advice. I'm leaving this issue here so future travels can be aware, and so we can fill in the reason and blockers.

To do so @rwjblue I likely need some of your context.

@Turbo87
Copy link
Member

Turbo87 commented Feb 27, 2019

@stefanpenner I think I managed to understand some of the context now:

  • ember-cli-preprocess-registry is a direct dependency of ember-cli (which means users can't update it themselves)
  • ember-cli passes the minifyCSS options to ember-cli-preprocess-registry, which in turn gets passed directly to clean-css
  • master of this project no longer has the clean-css fallback
  • in the end this means that we can't release a breaking change here without having to bump major for Ember CLI too :(

@jrjohnson
Copy link

Github started notifying me today that several of my ember addons have a vulnerability for clean-css < 4.1.11 clean-css/clean-css@2929baf I have no idea if it's a problem (not sure how clean-css is used) but given the way github screams about these alerts I wanted to mention it here.

@btecu
Copy link
Contributor

btecu commented Jul 20, 2019

I'm also getting the same warnings as @jrjohnson. What's the path forward?

@DuBistKomisch
Copy link

maybe a 3.3.1 with broccoli-clean-css bumped?

@gorner
Copy link

gorner commented Sep 11, 2019

@DuBistKomisch Looks like bumping broccoli-clean-css was attempted previously but had to be reverted: #27 (comment)

@rogeraraujo90
Copy link

@stefanpenner I can see that security issue is already fixed. Can this version be published now? Yarn Audit is blocking the CI in my project.

Thank you!

@gorner
Copy link

gorner commented Jan 14, 2020

@rogeraraujo90 The issue at this point is that the security bug (which has no actual impact on your Ember app in the browser) was only fixed in the 4.x stream of clean-css whereas this dependency relies on clean-css v3.x. There are some breaking changes in the clean-css config options from v3 to v4, so it can't be updated here without causing a breaking change to Ember CLI.

As suggested in the linked ember-cli issue above (ember-cli/ember-cli#8579) your best bet is likely to add the updated clean-css to your yarn resolutions in package.json:

"resolutions": {
  "clean-css": "4.2.1"
}

And then address any breaking changes that may be needed to any config options under the minifyCSS key in your app's ember-cli-build.js file.

@rogeraraujo90
Copy link

Thank you for the fast response @gorner! I'll proceed with your suggested workaround while wait for Ember 4.

@kategengler
Copy link
Member

I want to re-release 4.0.0 and update the dependency for ember-cli 5.0. We can document how to add back the exact old clean-css behavior and also how to use the newest clean-css instead.

@kategengler
Copy link
Member

Closing as I have now re-released the 4.x changes in 5.0(.1). ember-cli/ember-cli#10244 Updates in ember-cli.

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

No branches or pull requests

8 participants