Not possible to stay on older version (0.3.5)

[strandoe]

Here are our polymer dependencies in bower:
"polymer": "Polymer/polymer#0.3.5",
"core-elements": "Polymer/core-elements#0.3.5",
"paper-elements": "Polymer/paper-elements#0.3.5"

This still ends up loading a lot of 0.4.0 components and we are warned of a conflict between polymer versions:

Please note that,
core-elements#0.3.5, core-layout#0.3.5, paper-elements#0.3.5 depends on polymer#>=0.3.0 <1.0.0 which resolved to polymer#0.3.5
operations depends on polymer#0.3.5 which resolved to polymer#0.3.5
core-ajax#0.4.0, core-animated-pages#0.4.0, core-animation#0.4.0, core-collapse#0.4.0, core-component-page#0.4.0, core-dropdown#0.4.0, core-field#0.4.0, core-header-panel#0.4.0, core-icons#0.4.0, core-iconset#0.4.0, core-iconset-svg#0.4.0, core-input#0.4.0, core-layout-grid#0.4.0, core-layout-trbl#0.4.0, core-list#0.4.0, core-localstorage#0.4.0, core-media-query#0.4.0, core-menu-button#0.4.0, core-meta#0.4.0, core-overlay#0.4.0, core-popup-menu#0.4.0, core-range#0.4.0, core-selection#0.4.0, core-selector#0.4.0, core-shared-lib#0.4.0, core-signals#0.4.0, core-splitter#0.4.0, core-style#0.4.0, core-tooltip#0.4.0, core-transition#0.4.0, marked-element#0.4.0, paper-button#0.4.0, paper-dialog#0.4.0, paper-fab#0.4.0, paper-focusable#0.4.0, paper-icon-button#0.4.0, paper-input#0.4.0, paper-item#0.4.0, paper-menu-button#0.4.0, paper-shadow#0.4.0, prettify-element#0.4.0 depends on polymer#>=0.4.0 <1.0.0 which resolved to polymer#0.4.0
Resort to using polymer#0.3.5 which resolved to polymer#0.3.5
Code incompatibilities may occur.

[ebidel]

@azakus do we have a good strategy for installing a particular version of polymer (element set and all)? Even we update core-elements to fetch a particular version (e.g. #0.3.5), the element deps may resolve to something different (e.g. >=0.3.0 <1.0.0). Right?

[dfreedm]

No, there's no good way to install something like 0.3.5 for every element. Some elements are not updated that frequently.

@strandoe Sorry about that. I planned the dependency ranges to be flexible, but < 1.0.0 is clearly too flexible. I can make a 0.3.6 release that is just 0.3.5 with all the dependencies fixed to 0.3.x.
Starting from 0.4.1 the default range will just include the latest "major" version.

[dfreedm]

Ok, I have released a 0.3.6 tag that has correct version dependencies for core and paper elements. Let me know if any elements that you depend on need to be fixed as well