chore(deps): update many non-major

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
browser-sync (source)	^2.27.7 -> ^2.29.3					devDependencies	minor
firebase-functions	^3.18.0 -> ^3.24.1					dependencies	minor
lots0logs/gh-action-get-changed-files	2.1.4 -> 2.2.2					action	minor

---

Release Notes

BrowserSync/browser-sync (browser-sync)

v2.29.3: The one that fixes snippetOptions

Compare Source

What's Changed

• fix: append to head if body not present yet - fixes #​2031 by @​shakyShane in https://github.com/BrowserSync/browser-sync/pull/2041

Full Changelog: BrowserSync/browser-sync@v2.29.2...v2.29.3

v2.29.2

Compare Source

v2.29.1

Compare Source

What's Changed

• trim-deps by @​shakyShane in https://github.com/BrowserSync/browser-sync/pull/2028

Full Changelog: BrowserSync/browser-sync@v2.29.0...v2.29.1

v2.29.0: The one that restores IE11 support 💪

Compare Source

What's Changed

• fix ie11 by @​shakyShane in https://github.com/BrowserSync/browser-sync/pull/2024

esbuild does not support down-level transpiling as far as IE11 - so when I switched to it, it accidentally broke IE11 support 😢

This is an important issue for me - many devs that support old browsers like IE11 are doing so because their projects are used in public services, or internal applications. Not every developer out there has the luxury of supporting evergreen-only browsers.

So, IE11 will work once again 🎉. Please use the issues thread to make me aware of any problem that's preventing you from using Browsersync in your day job 💪 (and be sure to thumbs-up the issues you want to see resolved)

### IE11 works, again
npm install browser-sync@latest

Full Changelog: BrowserSync/browser-sync@v2.28.3...v2.29.0

v2.28.3

Compare Source

v2.28.2

Compare Source

v2.28.1

Compare Source

v2.28.0: the one that finally removes document.write

Compare Source

What's Changed

• browser-sync-2017 use chalk everywhere by @​shakyShane in https://github.com/BrowserSync/browser-sync/pull/2018
• fix: remove document.write by @​shakyShane in https://github.com/BrowserSync/browser-sync/pull/2019

Full Changelog: BrowserSync/browser-sync@v2.27.12...v2.28.0

v2.27.12

Compare Source

v2.27.11

Compare Source

v2.27.10

Compare Source

v2.27.9: 2.27.9

Compare Source

What's Changed

• fix(cli): Where's the command help? fixes #​1929 by @​shakyShane in https://github.com/BrowserSync/browser-sync/pull/1945

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: 2.27.8

Compare Source

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

PR:

• BrowserSync/browser-sync@58ab4ab

Resolved Issues:

• https://github.com/BrowserSync/browser-sync/issues/1850
• https://github.com/BrowserSync/browser-sync/issues/1892
• https://github.com/BrowserSync/browser-sync/issues/1925
• https://github.com/BrowserSync/browser-sync/issues/1926
• https://github.com/BrowserSync/browser-sync/issues/1933

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

firebase/firebase-functions (firebase-functions)

v3.24.1

Compare Source

• Fix reference docs for performance monitoring.
• Fix bug where function configuration wil null values couldn't be deployed. (#​1246)

v3.24.0

Compare Source

• Add performance monitoring triggers to v2 alerts (#​1223).

v3.23.0

Compare Source

• Fixes a bug that disallowed setting customClaims and/or sessionClaims in blocking functions (#​1199).
• Add v2 Schedule Triggers (#​1177).

v3.22.0

Compare Source

• Adds RTDB Triggers for v2 functions (#​1127)
• Adds support for Firebase Admin SDK v11 (#​1151)
• Fixes bug where emulated task queue function required auth header (#​1154)

v3.21.2

Compare Source

• Fixes bug where toJSON was not defined in UserRecord (#​1125).

v3.21.1

Compare Source

• Add debug feature to enable cors option for v2 onRequest and onCall handlers. (#​1099)

v3.21.0

Compare Source

• Adds CPU option and enhances internal data structures (#​1077)
• Add auth blocking handlers (#​1080)
• Add support for secrets in v2 (#​1079)
• Update types for AlertPayloads (#​1087)
• Update AppDistribution [@type] (#​1088)
• Update CloudEvent types (#​1089)
• Generate documentation with api-extractor (#​1071)
• Change type info to be inheritance friendly. (#​1091)
• Changes the memory options from MB to MiB and GB to GiB for greater clarity (#​1090)

v3.20.1

Compare Source

• Improve authorization for tasks. (#​1073)

v3.20.0

Compare Source

• Changes internal structure to be more flexible (#​1070).

v3.19.0

Compare Source

• Add support for more regions and memory for v2 functions (#​1037).
• Fixes bug where some RTDB instance names were incorrectly parsed (#​1056).

v3.18.1

Compare Source

• Expose stack YAML via __/functions.yaml endpoint instead (#​1036).

lots0logs/gh-action-get-changed-files (lots0logs/gh-action-get-changed-files)

v2.2.2: [FIX]: v2.2.2

Compare Source

v2.2.1: [MAINTENANCE] v2.2.1

Compare Source

v2.2.0: [MAINTENANCE] v2.2.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "after 6am and before 10am on monday" (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Images automagically compressed by Calibre's image-actions ✨

Compression reduced images by 3.3%, saving 296 bytes.

Filename	Before	After	Improvement	Visual comparison
template/public/img/uploads/rect89.webp	8.73 KB	8.44 KB	-3.3%	View diff

51 images did not require optimisation.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.