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 dependency browser-sync to v2.27.10 - autoclosed #3

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 3, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
browser-sync (source) ^2.26.7 -> 2.27.10 age adoption passing confidence

Release Notes

BrowserSync/browser-sync

v2.27.10

Compare Source

v2.27.9

Compare Source

What's Changed

A bug prevented the help output from displaying - it was introduced when the CLI parser yargs was updated, and is now fixed :)

Full Changelog: BrowserSync/browser-sync@v2.27.8...v2.27.9

v2.27.8

Compare Source

This release upgrades Socket.io (client+server) to the latest versions - solving the following issues, and silencing security warning :)

PR:

Resolved Issues:

Thanks to @​lachieh for the original PR, which helped me land this fix

v2.27.7

Compare Source

v2.27.6

Compare Source

v2.27.5

Compare Source

v2.27.4

Compare Source

v2.27.3

Compare Source

v2.27.1

Compare Source

This release adds a feature to address https://github.com/BrowserSync/browser-sync/issues/1882

Sometimes you don't want Browsersync to auto-inject it's connection snippet into your HTML - now you can disable it globally via either a CLI param or the new snippet option :)

browser-sync . --no-snippet

or in any Browsersync configuration

const config = {
  snippet: false,
};

the original request was related to Eleventy usage, so here's how that would look

eleventyConfig.setBrowserSyncConfig({
  snippet: false,
});

v2.26.14

Compare Source

This is a maintenance release to address 2 security related issues (socket.io & axios)

Happy Browsersync'in :)

v2.26.13

Compare Source

v2.26.12

Compare Source

v2.26.10

Compare Source

v2.26.9

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/browser-sync-2.x branch from a2728f3 to 753136f Compare February 23, 2022 08:02
@renovate renovate bot force-pushed the renovate/browser-sync-2.x branch from 753136f to ae028aa Compare March 13, 2022 21:43
@renovate renovate bot changed the title Update dependency browser-sync to v2.27.7 Update dependency browser-sync to v2.27.8 Mar 13, 2022
@renovate renovate bot force-pushed the renovate/browser-sync-2.x branch from ae028aa to 350e834 Compare March 15, 2022 10:10
@renovate renovate bot changed the title Update dependency browser-sync to v2.27.8 Update dependency browser-sync to v2.27.9 Mar 15, 2022
@renovate renovate bot force-pushed the renovate/browser-sync-2.x branch from 350e834 to ac5aafd Compare June 18, 2022 21:15
@renovate renovate bot changed the title Update dependency browser-sync to v2.27.9 Update dependency browser-sync to v2.27.10 Jun 18, 2022
@renovate renovate bot changed the title Update dependency browser-sync to v2.27.10 Update dependency browser-sync to v2.27.10 - autoclosed Nov 20, 2022
@renovate renovate bot closed this Nov 20, 2022
@renovate renovate bot deleted the renovate/browser-sync-2.x branch November 20, 2022 14:50
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.

None yet

0 participants