Update postcss-syntax postcss-markdown postcss-html to the latest version 🚀 #3331
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
ntwb
approved these changes
May 24, 2018
Version 0.25.0 just got published.Update to this version instead 🚀 Release Notesv0.25.0
|
Version 0.26.0 just got published. |
gucong3000
approved these changes
May 28, 2018
fix(package): update postcss-syntax to version 0.26.0 fix(package): update postcss-markdown to version 0.26.0 fix(package): update postcss-html to version 0.26.0
gucong3000
force-pushed
the
greenkeeper/postcss-syntax-0.24.0
branch
from
6a21c75
to
1cf3160
Compare
gucong3000
changed the title
Version 0.26.1 just got published.Update to this version instead 🚀 Release Notesv0.26.1
|
This was referenced May 28, 2018
|
cc @ntwb |
bors bot
referenced
this pull request
in mozilla/delivery-console
Jun 15, 2018
194: Update dependency stylelint to v9.3.0 r=rehandalal a=renovate[bot] This Pull Request updates dependency [stylelint](https://github.com/stylelint/stylelint) from `v9.2.1` to `v9.3.0` <details> <summary>Release Notes</summary> ### [`v9.3.0`](https://github.com/stylelint/stylelint/blob/master/CHANGELOG.md#​930) [Compare Source](stylelint/stylelint@9.2.1...9.3.0) - Added: support for `<style>` tags and `style=""` attributes in XML and XSLT files ([#​3386](`https://github.com/stylelint/stylelint/pull/3386`)). - Added: `globbyOptions` option ([#​3339](`https://github.com/stylelint/stylelint/pull/3339`)). - Added: `keyframes-name-pattern` rule ([#​3321](`https://github.com/stylelint/stylelint/pull/3321`)). - Added: `media-feature-name-value-whitelist` rule ([#​3320](`https://github.com/stylelint/stylelint/pull/3320`)). - Added: `selector-pseudo-element-colon-notation` autofix ([#​3345](`https://github.com/stylelint/stylelint/pull/3345`)). - Fixed: `.vue` files throwing errors for `<style lang="stylus">` and `<style lang="postcss">` ([#​3331](`https://github.com/stylelint/stylelint/pull/3331`)). - Fixed: `declaration-block-no-*` false positives for non-standard syntax ([#​3381](`https://github.com/stylelint/stylelint/pull/3381`)). - Fixed: `function-whitespace-after` false positives for "/" ([#​3132](`https://github.com/stylelint/stylelint/pull/3132`)). - Fixed: `length-zero-no-unit` incorrect autofix for at-includes ([#​3347](`https://github.com/stylelint/stylelint/pull/3347`)). - Fixed: `max-nesting-depth` false positives for nested properties ([#​3349](`https://github.com/stylelint/stylelint/pull/3349`)). - Fixed: `no-empty-source` false positives on vue external sources `<style src="*">` tag ([#​3331](`https://github.com/stylelint/stylelint/pull/3331`)). - Fixed: `max-line-length` false positives for non-CSS blocks ([#​3367](`https://github.com/stylelint/stylelint/pull/3367`)). - Fixed: `no-eol-whitespace` false positives for non-CSS blocks ([#​3367](`https://github.com/stylelint/stylelint/pull/3367`)). - Fixed: `no-extra-semicolons` false positives for non-CSS blocks ([#​3367](`https://github.com/stylelint/stylelint/pull/3367`)). - Fixed: `no-missing-end-of-source-newline` false positives for non-CSS blocks ([#​3367](`https://github.com/stylelint/stylelint/pull/3367`)). --- </details> --- This PR has been generated by [Renovate Bot](https://renovatebot.com). Co-authored-by: Renovate Bot <[email protected]>
schalkneethling
referenced
this pull request
in mdn/interactive-examples
Jun 16, 2018
This Pull Request updates dependency [stylelint](https://github.com/stylelint/stylelint) from `v9.2.1` to `v9.3.0` <details> <summary>Release Notes</summary> ### [`v9.3.0`](https://github.com/stylelint/stylelint/blob/master/CHANGELOG.md#​930) [Compare Source](stylelint/stylelint@9.2.1...9.3.0) - Added: support for `<style>` tags and `style=""` attributes in XML and XSLT files ([#​3386](`https://github.com/stylelint/stylelint/pull/3386`)). - Added: `globbyOptions` option ([#​3339](`https://github.com/stylelint/stylelint/pull/3339`)). - Added: `keyframes-name-pattern` rule ([#​3321](`https://github.com/stylelint/stylelint/pull/3321`)). - Added: `media-feature-name-value-whitelist` rule ([#​3320](`https://github.com/stylelint/stylelint/pull/3320`)). - Added: `selector-pseudo-element-colon-notation` autofix ([#​3345](`https://github.com/stylelint/stylelint/pull/3345`)). - Fixed: `.vue` files throwing errors for `<style lang="stylus">` and `<style lang="postcss">` ([#​3331](`https://github.com/stylelint/stylelint/pull/3331`)). - Fixed: `declaration-block-no-*` false positives for non-standard syntax ([#​3381](`https://github.com/stylelint/stylelint/pull/3381`)). - Fixed: `function-whitespace-after` false positives for "/" ([#​3132](`https://github.com/stylelint/stylelint/pull/3132`)). - Fixed: `length-zero-no-unit` incorrect autofix for at-includes ([#​3347](`https://github.com/stylelint/stylelint/pull/3347`)). - Fixed: `max-nesting-depth` false positives for nested properties ([#​3349](`https://github.com/stylelint/stylelint/pull/3349`)). - Fixed: `no-empty-source` false positives on vue external sources `<style src="*">` tag ([#​3331](`https://github.com/stylelint/stylelint/pull/3331`)). - Fixed: `max-line-length` false positives for non-CSS blocks ([#​3367](`https://github.com/stylelint/stylelint/pull/3367`)). - Fixed: `no-eol-whitespace` false positives for non-CSS blocks ([#​3367](`https://github.com/stylelint/stylelint/pull/3367`)). - Fixed: `no-extra-semicolons` false positives for non-CSS blocks ([#​3367](`https://github.com/stylelint/stylelint/pull/3367`)). - Fixed: `no-missing-end-of-source-newline` false positives for non-CSS blocks ([#​3367](`https://github.com/stylelint/stylelint/pull/3367`)). --- </details> --- This PR has been generated by [Renovate Bot](https://renovatebot.com).
This was referenced Jun 17, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 0.24.0 of postcss-syntax was just published.
postcss-syntaxThe version 0.24.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of postcss-syntax.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v0.24.0postcss-jsx(#17)FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴