ubyssey.ca
ubyssey.ca copied to clipboard
Bump semver, node-sass and core-js-compat in /ubyssey/static_src
Bumps semver to 5.7.2 and updates ancestor dependencies semver, node-sass and core-js-compat. These dependencies need to be updated together.
Updates semver
from 5.7.1 to 5.7.2
Release notes
Sourced from semver's releases.
v5.7.2
5.7.2 (2023-07-10)
Bug Fixes
2f8fd41
#585 better handling of whitespace (#585) (@joaomoreno
,@lukekarrys
)
Changelog
Sourced from semver's changelog.
5.7.2 (2023-07-10)
Bug Fixes
2f8fd41
#585 better handling of whitespace (#585) (@joaomoreno
,@lukekarrys
)5.7
- Add
minVersion
method5.6
- Move boolean
loose
param to an options object, with backwards-compatibility protection.- Add ability to opt out of special prerelease version handling with the
includePrerelease
option flag.5.5
- Add version coercion capabilities
5.4
- Add intersection checking
5.3
- Add
minSatisfying
method5.2
- Add
prerelease(v)
that returns prerelease components5.1
- Add Backus-Naur for ranges
- Remove excessively cute inspection methods
5.0
- Remove AMD/Browserified build artifacts
- Fix ltr and gtr when using the
*
range- Fix for range
*
with a prerelease identifier
Commits
Maintainer changes
This version was pushed to npm by lukekarrys, a new releaser for semver since your current version.
Updates node-sass
from 4.14.1 to 9.0.0
Release notes
Sourced from node-sass's releases.
v9.0.0
What's Changed
- Node 20 support by
@nschonni
in sass/node-sass#3355Breaking changes
- Drop support for Node 14 (
@nschonni
)Supported Environments
OS Architecture Node Windows x86 & x64 16, 18, 19, 20 OSX x64 16, 18, 19, 20 Linux* x64 16, 18, 19, 20 Alpine Linux x64 16, 18, 19, 20 *Linux support refers to major distributions like Ubuntu, and Debian
v8.0.0
What's Changed
- Fix binaries being partially downloaded by
@xzyfer
in sass/node-sass#3313- Bump node-gyp and nan for node 19 support by
@xzyfer
in sass/node-sass#3314- feat: Node 18 and 19 support and drop Node 17 by
@nschonni
in sass/node-sass#3257Breaking changes
- Drop support for Node 12 (
@nschonni
)- Drop support for Node 17 (
@nschonni
)- Set
rejectUnauthorized
totrue
by default (@scott-ut
, #3149)Features
- Add support for Node 18 (
@nschonni
)- Add support for Node 19 (
@nschonni
)- Replace
request
withmake-fetch-happen
(@CamilleDrapier
@xzyfer
, #3193, #3313)Dependencies
- Bump [email protected]
- Bump node-gyp
@9
.0.0- Bump nan@^2.17.0
- Bump sass-graph@^4.0.1
Misc
- Bump various GitHub Actions dependencies (
@nschonni
)
... (truncated)
Commits
87f3899
feat: Node 20 support (#3355)06ae4c7
build(deps): bump coverallsapp/github-action from 2.0.0 to 2.1.0 (#3350)e069f73
build(deps): bump coverallsapp/github-action from 1.2.0 to 2.0.0c34837d
build(deps): bump coverallsapp/github-action from 1.1.3 to 1.2.0ee13eb9
8.0.098e75b3
feat: Node 18 and 19 support and drop Node 17 (#3257)e9bb866
Bump node-gyp and nan for node 19 support (#3314)ab7840b
Fix binaries being partially downloaded (#3313)d595abf
7.0.33b556c1
7.0.2- Additional commits viewable in compare view
Updates core-js-compat
from 3.6.5 to 3.31.1
Changelog
Sourced from core-js-compat's changelog.
3.31.1 - 2023.07.06
- Fixed a
structuredClone
bug with cloning views of transferred buffers, #1265- Fixed the order of arguments validation in
DataView
methods- Allowed cloning of
Float16Array
instructuredClone
- Compat data improvements:
Set
methods proposal marked as supported from Safari 17.0- New
URL
features:URL.canParse
,URLSearchParams.prototype.size
andvalue
argument ofURLSearchParams.prototype.{ has, delete }
marked as supported from Safari 17.0value
argument ofURLSearchParams.prototype.{ has, delete }
marked as supported from Deno 1.35AggregateError
and well-formedJSON.stringify
marked as supported React Native 0.72 Hermes- Added Deno 1.35 compat data mapping
- Added Quest Browser 28 compat data mapping
- Added missing NodeJS 12.16-12.22 compat data mapping
- Updated Opera Android 76 compat data mapping
3.31.0 - 2023.06.12
- Well-formed unicode strings proposal:
- Methods:
String.prototype.isWellFormed
methodString.prototype.toWellFormed
method- Moved to stable ES, May 2023 TC39 meeting
- Added
es.
namespace modules,/es/
and/stable/
namespaces entriesArray
grouping proposal, May 2023 TC39 meeting updates:
- Because of the web compat issue, moved from prototype to static methods. Added:
Object.groupBy
methodMap.groupBy
method (with the actual semantic - with a minor difference it was present in the collections methods stage 1 proposal)- Demoted to stage 2
- Decorator Metadata proposal, May 2023 TC39 meeting updates:
- Moved to stage 3
- Added
Function.prototype[Symbol.metadata]
(=== null
)- Added
/actual/
entries- Iterator Helpers stage 3 proposal:
- Changed
Symbol.iterator
fallback from callable check toundefined
/null
check, May 2023 TC39 meeting, proposal-iterator-helpers/272- Removed
IsCallable
check onNextMethod
, deferring errors toCall
site, May 2023 TC39 meeting, proposal-iterator-helpers/274- Added
Promise.withResolvers
stage 2 proposal:
Promise.withResolvers
methodSymbol
predicates stage 2 proposal:
- The methods renamed to end with
Symbol
, May 2023 TC39 meeting:
Symbol.isRegistered
->Symbol.isRegisteredSymbol
methodSymbol.isWellKnown
->Symbol.isWellKnownSymbol
method- Added
value
argument ofURLSearchParams.prototype.{ has, delete }
, url/735- Fixed some cases of increasing buffer size in
ArrayBuffer.prototype.{ transfer, transferToFixedLength }
polyfills- Fixed awaiting async
AsyncDisposableStack.prototype.adopt
callback, #1258- Fixed
URLSearchParams#size
in ES3 engines (IE8-)- Added a workaround in
Object.{ entries, values }
for some IE versions bug with invisible integer keys onnull
-prototype objects- Added TypeScript definitions to
core-js-compat
, #1235, thanks@susnux
- Compat data improvements:
Set.prototype.difference
that was missed in Bun because of a bug added in 0.6.0Array.prototype.{ group, groupToMap }
marked as no longer supported in WebKit runtimes because of the mentioned above web compat issue. For example, it's disabled from Bun 0.6.2- Methods from the change
Array
by copy proposal marked as supported from FF115Array.fromAsync
marked as supported from FF115
... (truncated)
Commits
9376c6f
3.31.180b2e80
add Deno 1.35 compat data mappingf2b351a
markvalue
argument ofURLSearchParams.prototype.{ has, delete }
as suppo...60d91f8
add a link2adeff0
update Opera Android 76 compat data mapping74eaa4b
add Quest Browser 28 compat data mapping74716af
add missing NodeJS 12.16-12.22 compat data mapping4f96175
add React Native 0.72 Hermes compat dataaaa2e4a
update dependencieseef0929
update dependencies- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.
This is something we should consider. After a bit of reading on npm I have realized that node-sass and the node are not compatible. Therefore, any weird behaviors' from the sass are possibly coming from here, not to mention other places.
Will reassess after deployment of pull release #1153